youngtube.nl

youngtube.nl may not be SSL secured

Free website and domain report on youngtube.nl

Last Updated: 2nd March, 2023 Update Now
Overview

Snoop Summary for youngtube.nl

This is a free and comprehensive report about youngtube.nl. The domain youngtube.nl is currently hosted on a server located in Netherlands with the IP address 185.104.29.70, where EUR is the local currency and the local language is Dutch. Youngtube.nl has the potential to be earning an estimated $1 USD per day from advertising revenue. If youngtube.nl was to be sold it would possibly be worth $799 USD (based on the daily revenue potential of the website over a 24 month period). Youngtube.nl is somewhat popular with an estimated 379 daily unique visitors. This report was last updated 2nd March, 2023.

About youngtube.nl

Site Preview: youngtube.nl youngtube.nl
Title: Home
Description:
Keywords and Tags: marketing, merchandising
Related Terms: youngtube
Fav Icon:
Age: Over 5 years old
Domain Created: 28th October, 2018
Domain Updated: 12th May, 2020
Domain Expires:
Review

Snoop Score

1/5

Valuation

$799 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,235,157
Alexa Reach: <0.0001%
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 379
Monthly Visitors: 11,536
Yearly Visitors: 138,335
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $33 USD
Yearly Revenue: $394 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: youngtube.nl 12
Domain Name: youngtube 9
Extension (TLD): nl 2

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 73
Performance 95
Accessibility 84
Best Practices 83
SEO 80
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
95

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for youngtube.nl. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 1.1 s
The time taken for the page to become fully interactive.
Speed Index — 1.1 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 1.1 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://youngtube.nl/
http/1.1
0
31.705999979749
1608
3430
200
text/html
Document
http://youngtube.nl/assets/web/assets/mobirise-icons/mobirise-icons.css
http/1.1
45.131999999285
80.033999984153
1951
7613
200
text/css
Stylesheet
http://youngtube.nl/assets/web/assets/mobirise-icons2/mobirise2.css
http/1.1
46.746999985771
91.586999973515
2034
8709
200
text/css
Stylesheet
http://youngtube.nl/assets/bootstrap/css/bootstrap.min.css
http/1.1
46.820999996271
98.649999999907
23363
153182
200
text/css
Stylesheet
http://youngtube.nl/assets/bootstrap/css/bootstrap-grid.min.css
http/1.1
46.880999987479
83.699999988312
6413
48488
200
text/css
Stylesheet
http://youngtube.nl/assets/bootstrap/css/bootstrap-reboot.min.css
http/1.1
46.951999975136
86.816999973962
1956
3836
200
text/css
Stylesheet
http://youngtube.nl/assets/tether/tether.min.css
http/1.1
47.016999975313
86.645999981556
510
237
200
text/css
Stylesheet
http://youngtube.nl/assets/theme/css/style.css
http/1.1
47.084999998333
72.455999994418
4435
23306
200
text/css
Stylesheet
http://youngtube.nl/assets/mobirise/css/mbr-additional.css
http/1.1
47.147999983281
84.250999992946
3760
18019
200
text/css
Stylesheet
http://youngtube.nl/assets/web/assets/jquery/jquery.min.js
http/1.1
47.217999992426
98.255999997491
33686
95931
200
application/javascript
Script
http://youngtube.nl/assets/popper/popper.min.js
http/1.1
50.387999974191
84.611999976914
7229
18994
200
application/javascript
Script
http://youngtube.nl/assets/bootstrap/js/bootstrap.min.js
http/1.1
50.499999983003
104.60099999909
14954
55775
200
application/javascript
Script
http://youngtube.nl/assets/tether/tether.min.js
http/1.1
50.610999984201
89.728999999352
7272
23217
200
application/javascript
Script
http://youngtube.nl/assets/smoothscroll/smooth-scroll.js
http/1.1
50.688999996055
84.453999996185
7406
25569
200
application/javascript
Script
http://youngtube.nl/assets/parallax/jarallax.min.js
http/1.1
50.750999973388
85.867999994662
5471
15471
200
application/javascript
Script
http://youngtube.nl/assets/theme/js/script.js
http/1.1
50.814999995055
89.98900000006
9858
49451
200
application/javascript
Script
http://youngtube.nl/assets/formoid/formoid.min.js
http/1.1
50.879999995232
97.879999986617
2704
10129
200
application/javascript
Script
https://fonts.googleapis.com/css?family=Rubik:300,300i,400,400i,500,500i,700,700i,900,900i&display=swap
h2
99.650999996811
112.08500000066
1454
16255
200
text/css
Stylesheet
http://youngtube.nl/assets/images/mbr-1920x1279.jpg
http/1.1
155.72799998336
219.51899997657
616958
616628
200
image/jpeg
Image
https://fonts.gstatic.com/s/rubik/v23/iJWKBXyIfDnIV7nBrXyw023e.woff2
h2
155.82899999572
167.04699999536
34660
33848
200
font/woff2
Font
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
35.992
13.005
95.386
6.909
110.578
16.512
128.929
20.084
149.021
20.045
169.354
46.3
218.309
14.899
233.555
22.826
260.347
15.706
276.061
10.005
286.157
39.024
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Youngtube.nl should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Youngtube.nl should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Youngtube.nl should consider minifying CSS files.
Minify JavaScript — Potential savings of 8 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Youngtube.nl should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://youngtube.nl/assets/theme/js/script.js
9858
4836
http://youngtube.nl/assets/smoothscroll/smooth-scroll.js
7406
3805
Reduce unused CSS — Potential savings of 21 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Youngtube.nl should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://youngtube.nl/assets/bootstrap/css/bootstrap.min.css
23363
21662
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 126 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://youngtube.nl/assets/images/mbr-1920x1279.jpg
616628
129495.65
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 30 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://youngtube.nl/
32.691
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Youngtube.nl should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Youngtube.nl should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://youngtube.nl/assets/popper/popper.min.js
64
http://youngtube.nl/assets/parallax/jarallax.min.js
59
http://youngtube.nl/assets/tether/tether.min.js
58
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 769 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://youngtube.nl/assets/images/mbr-1920x1279.jpg
616958
https://fonts.gstatic.com/s/rubik/v23/iJWKBXyIfDnIV7nBrXyw023e.woff2
34660
http://youngtube.nl/assets/web/assets/jquery/jquery.min.js
33686
http://youngtube.nl/assets/bootstrap/css/bootstrap.min.css
23363
http://youngtube.nl/assets/bootstrap/js/bootstrap.min.js
14954
http://youngtube.nl/assets/theme/js/script.js
9858
http://youngtube.nl/assets/smoothscroll/smooth-scroll.js
7406
http://youngtube.nl/assets/tether/tether.min.js
7272
http://youngtube.nl/assets/popper/popper.min.js
7229
http://youngtube.nl/assets/bootstrap/css/bootstrap-grid.min.css
6413
Avoids an excessive DOM size — 46 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
46
Maximum DOM Depth
9
Maximum Child Elements
14
Avoid chaining critical requests — 15 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Youngtube.nl should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://youngtube.nl/assets/parallax/jarallax.min.js
86.839
26.706
0.355
http://youngtube.nl/
80.935
5.42
1.029
http://youngtube.nl/assets/web/assets/jquery/jquery.min.js
53.292
37.314
5.136
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
91.544
Rendering
70.892
Other
66.035
Style & Layout
31.861
Parse HTML & CSS
25.409
Script Parsing & Compilation
13.58
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 20 requests • 769 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
20
787682
Image
1
616958
Script
8
88580
Stylesheet
9
45876
Font
1
34660
Document
1
1608
Media
0
0
Other
0
0
Third-party
2
36114
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
36114
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00019614908939673
0.00013610344978548
8.006085281499E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of youngtube.nl on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 1.1 s
The time taken for the first image or text on the page to be rendered.

Audits

First Meaningful Paint — 1.1 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 530 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Youngtube.nl should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://youngtube.nl/assets/web/assets/mobirise-icons/mobirise-icons.css
1951
70
http://youngtube.nl/assets/web/assets/mobirise-icons2/mobirise2.css
2034
110
http://youngtube.nl/assets/bootstrap/css/bootstrap.min.css
23363
230
http://youngtube.nl/assets/bootstrap/css/bootstrap-grid.min.css
6413
110
http://youngtube.nl/assets/bootstrap/css/bootstrap-reboot.min.css
1956
110
http://youngtube.nl/assets/tether/tether.min.css
510
110
http://youngtube.nl/assets/theme/css/style.css
4435
70
Serve static assets with an efficient cache policy — 17 resources found
Youngtube.nl can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://youngtube.nl/assets/images/mbr-1920x1279.jpg
691200000
616958
http://youngtube.nl/assets/web/assets/jquery/jquery.min.js
691200000
33686
http://youngtube.nl/assets/bootstrap/css/bootstrap.min.css
691200000
23363
http://youngtube.nl/assets/bootstrap/js/bootstrap.min.js
691200000
14954
http://youngtube.nl/assets/theme/js/script.js
691200000
9858
http://youngtube.nl/assets/smoothscroll/smooth-scroll.js
691200000
7406
http://youngtube.nl/assets/tether/tether.min.js
691200000
7272
http://youngtube.nl/assets/popper/popper.min.js
691200000
7229
http://youngtube.nl/assets/bootstrap/css/bootstrap-grid.min.css
691200000
6413
http://youngtube.nl/assets/parallax/jarallax.min.js
691200000
5471
http://youngtube.nl/assets/theme/css/style.css
691200000
4435
http://youngtube.nl/assets/mobirise/css/mbr-additional.css
691200000
3760
http://youngtube.nl/assets/formoid/formoid.min.js
691200000
2704
http://youngtube.nl/assets/web/assets/mobirise-icons2/mobirise2.css
691200000
2034
http://youngtube.nl/assets/bootstrap/css/bootstrap-reboot.min.css
691200000
1956
http://youngtube.nl/assets/web/assets/mobirise-icons/mobirise-icons.css
691200000
1951
http://youngtube.nl/assets/tether/tether.min.css
691200000
510
84

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of youngtube.nl. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Youngtube.nl may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that youngtube.nl should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.2.1
jQuery
1.11.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
http://youngtube.nl/assets/parallax/jarallax.min.js
http://youngtube.nl/assets/parallax/jarallax.min.js.map
http://youngtube.nl/assets/bootstrap/js/bootstrap.min.js
http://youngtube.nl/assets/bootstrap/js/bootstrap.min.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 18 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://youngtube.nl/
Allowed
http://youngtube.nl/assets/web/assets/mobirise-icons/mobirise-icons.css
Allowed
http://youngtube.nl/assets/web/assets/mobirise-icons2/mobirise2.css
Allowed
http://youngtube.nl/assets/bootstrap/css/bootstrap.min.css
Allowed
http://youngtube.nl/assets/bootstrap/css/bootstrap-grid.min.css
Allowed
http://youngtube.nl/assets/bootstrap/css/bootstrap-reboot.min.css
Allowed
http://youngtube.nl/assets/tether/tether.min.css
Allowed
http://youngtube.nl/assets/theme/css/style.css
Allowed
http://youngtube.nl/assets/mobirise/css/mbr-additional.css
Allowed
http://youngtube.nl/assets/web/assets/jquery/jquery.min.js
Allowed
http://youngtube.nl/assets/popper/popper.min.js
Allowed
http://youngtube.nl/assets/bootstrap/js/bootstrap.min.js
Allowed
http://youngtube.nl/assets/tether/tether.min.js
Allowed
http://youngtube.nl/assets/smoothscroll/smooth-scroll.js
Allowed
http://youngtube.nl/assets/parallax/jarallax.min.js
Allowed
http://youngtube.nl/assets/theme/js/script.js
Allowed
http://youngtube.nl/assets/formoid/formoid.min.js
Allowed
http://youngtube.nl/assets/images/mbr-1920x1279.jpg
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
1
Medium
4
Medium
80

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for youngtube.nl. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of youngtube.nl on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Crawling and Indexing

robots.txt is not valid — Request for robots.txt returned HTTP status: 500
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
22

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of youngtube.nl. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of youngtube.nl on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 74
Performance 82
Accessibility 92
Best Practices 83
SEO 83
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
82

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for youngtube.nl. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 3.6 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.002
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://youngtube.nl/
http/1.1
0
29.94200005196
1608
3430
200
text/html
Document
http://youngtube.nl/assets/web/assets/mobirise-icons/mobirise-icons.css
http/1.1
36.800000118092
63.074999954551
1951
7613
200
text/css
Stylesheet
http://youngtube.nl/assets/web/assets/mobirise-icons2/mobirise2.css
http/1.1
36.966999992728
64.201000146568
2034
8709
200
text/css
Stylesheet
http://youngtube.nl/assets/bootstrap/css/bootstrap.min.css
http/1.1
37.269999971613
83.390000043437
23363
153182
200
text/css
Stylesheet
http://youngtube.nl/assets/bootstrap/css/bootstrap-grid.min.css
http/1.1
37.513999966905
55.663000093773
6413
48488
200
text/css
Stylesheet
http://youngtube.nl/assets/bootstrap/css/bootstrap-reboot.min.css
http/1.1
37.670999998227
53.553000092506
1956
3836
200
text/css
Stylesheet
http://youngtube.nl/assets/tether/tether.min.css
http/1.1
37.922000046819
57.876999955624
510
237
200
text/css
Stylesheet
http://youngtube.nl/assets/theme/css/style.css
http/1.1
38.103000028059
66.483000060543
4435
23306
200
text/css
Stylesheet
http://youngtube.nl/assets/mobirise/css/mbr-additional.css
http/1.1
38.355000084266
64.710000064224
3760
18019
200
text/css
Stylesheet
http://youngtube.nl/assets/web/assets/jquery/jquery.min.js
http/1.1
38.627000059932
63.726000022143
33686
95931
200
application/javascript
Script
http://youngtube.nl/assets/popper/popper.min.js
http/1.1
38.859999971464
59.568000026047
7229
18994
200
application/javascript
Script
http://youngtube.nl/assets/bootstrap/js/bootstrap.min.js
http/1.1
38.987000007182
68.563000066206
14954
55775
200
application/javascript
Script
http://youngtube.nl/assets/tether/tether.min.js
http/1.1
39.190999930725
55.28900003992
7272
23217
200
application/javascript
Script
http://youngtube.nl/assets/smoothscroll/smooth-scroll.js
http/1.1
39.325000019744
60.235999990255
7406
25569
200
application/javascript
Script
http://youngtube.nl/assets/parallax/jarallax.min.js
http/1.1
39.532999973744
61.065000016242
5471
15471
200
application/javascript
Script
http://youngtube.nl/assets/theme/js/script.js
http/1.1
39.703000104055
72.241000132635
9858
49451
200
application/javascript
Script
http://youngtube.nl/assets/formoid/formoid.min.js
http/1.1
39.847000036389
65.958000021055
2704
10129
200
application/javascript
Script
https://fonts.googleapis.com/css?family=Rubik:300,300i,400,400i,500,500i,700,700i,900,900i&display=swap
h2
66.957999952137
74.417999945581
1454
16255
200
text/css
Stylesheet
http://youngtube.nl/assets/images/mbr-1920x1279.jpg
http/1.1
102.37600002438
147.82300009392
616958
616628
200
image/jpeg
Image
https://fonts.gstatic.com/s/rubik/v23/iJWKBXyIfDnIV7nBrXyw023e.woff2
h2
103.01299998537
106.67799995281
34660
33848
200
font/woff2
Font
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
33.23
9.723
88.524
11.466
99.997
11.97
112.004
16.963
131.054
5.61
137.053
7.929
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Youngtube.nl should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Youngtube.nl should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Youngtube.nl should consider minifying CSS files.
Minify JavaScript — Potential savings of 8 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Youngtube.nl should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://youngtube.nl/assets/theme/js/script.js
9858
4836
http://youngtube.nl/assets/smoothscroll/smooth-scroll.js
7406
3805
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 30 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://youngtube.nl/
30.933
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Youngtube.nl should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Youngtube.nl should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://youngtube.nl/assets/popper/popper.min.js
64
http://youngtube.nl/assets/parallax/jarallax.min.js
59
http://youngtube.nl/assets/tether/tether.min.js
58
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 769 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://youngtube.nl/assets/images/mbr-1920x1279.jpg
616958
https://fonts.gstatic.com/s/rubik/v23/iJWKBXyIfDnIV7nBrXyw023e.woff2
34660
http://youngtube.nl/assets/web/assets/jquery/jquery.min.js
33686
http://youngtube.nl/assets/bootstrap/css/bootstrap.min.css
23363
http://youngtube.nl/assets/bootstrap/js/bootstrap.min.js
14954
http://youngtube.nl/assets/theme/js/script.js
9858
http://youngtube.nl/assets/smoothscroll/smooth-scroll.js
7406
http://youngtube.nl/assets/tether/tether.min.js
7272
http://youngtube.nl/assets/popper/popper.min.js
7229
http://youngtube.nl/assets/bootstrap/css/bootstrap-grid.min.css
6413
Avoids an excessive DOM size — 44 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
44
Maximum DOM Depth
9
Maximum Child Elements
14
Avoid chaining critical requests — 15 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Youngtube.nl should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://youngtube.nl/
129.764
9.244
4.152
http://youngtube.nl/assets/web/assets/jquery/jquery.min.js
95.152
75.372
4.736
Unattributable
54.66
3.932
0
Minimizes main-thread work — 0.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
133.672
Other
114.444
Style & Layout
65.784
Parse HTML & CSS
36.604
Script Parsing & Compilation
21.916
Rendering
7.984
Garbage Collection
4.952
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 20 requests • 769 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
20
787682
Image
1
616958
Script
8
88580
Stylesheet
9
45876
Font
1
34660
Document
1
1608
Media
0
0
Other
0
0
Third-party
2
36114
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
36114
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0011308670043945
0.00078468322753906
0.00046157836914062
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of youngtube.nl on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Speed Index — 3.6 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 3.6 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 3.6 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused CSS — Potential savings of 22 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Youngtube.nl should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://youngtube.nl/assets/bootstrap/css/bootstrap.min.css
23363
22961
Serve images in next-gen formats — Potential savings of 126 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://youngtube.nl/assets/images/mbr-1920x1279.jpg
616628
129495.65
Serve static assets with an efficient cache policy — 17 resources found
Youngtube.nl can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://youngtube.nl/assets/images/mbr-1920x1279.jpg
691200000
616958
http://youngtube.nl/assets/web/assets/jquery/jquery.min.js
691200000
33686
http://youngtube.nl/assets/bootstrap/css/bootstrap.min.css
691200000
23363
http://youngtube.nl/assets/bootstrap/js/bootstrap.min.js
691200000
14954
http://youngtube.nl/assets/theme/js/script.js
691200000
9858
http://youngtube.nl/assets/smoothscroll/smooth-scroll.js
691200000
7406
http://youngtube.nl/assets/tether/tether.min.js
691200000
7272
http://youngtube.nl/assets/popper/popper.min.js
691200000
7229
http://youngtube.nl/assets/bootstrap/css/bootstrap-grid.min.css
691200000
6413
http://youngtube.nl/assets/parallax/jarallax.min.js
691200000
5471
http://youngtube.nl/assets/theme/css/style.css
691200000
4435
http://youngtube.nl/assets/mobirise/css/mbr-additional.css
691200000
3760
http://youngtube.nl/assets/formoid/formoid.min.js
691200000
2704
http://youngtube.nl/assets/web/assets/mobirise-icons2/mobirise2.css
691200000
2034
http://youngtube.nl/assets/bootstrap/css/bootstrap-reboot.min.css
691200000
1956
http://youngtube.nl/assets/web/assets/mobirise-icons/mobirise-icons.css
691200000
1951
http://youngtube.nl/assets/tether/tether.min.css
691200000
510

Metrics

First Contentful Paint — 3.6 s
The time taken for the first image or text on the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 1,410 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Youngtube.nl should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://youngtube.nl/assets/web/assets/mobirise-icons/mobirise-icons.css
1951
180
http://youngtube.nl/assets/web/assets/mobirise-icons2/mobirise2.css
2034
330
http://youngtube.nl/assets/bootstrap/css/bootstrap.min.css
23363
1080
http://youngtube.nl/assets/bootstrap/css/bootstrap-grid.min.css
6413
480
http://youngtube.nl/assets/bootstrap/css/bootstrap-reboot.min.css
1956
330
http://youngtube.nl/assets/tether/tether.min.css
510
330
http://youngtube.nl/assets/theme/css/style.css
4435
330
First Contentful Paint (3G) — 6840 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
92

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of youngtube.nl. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Youngtube.nl may provide assistance to deaf or hearing-impaired users with captions on videos.

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that youngtube.nl should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.2.1
jQuery
1.11.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
http://youngtube.nl/assets/parallax/jarallax.min.js
http://youngtube.nl/assets/parallax/jarallax.min.js.map
http://youngtube.nl/assets/bootstrap/js/bootstrap.min.js
http://youngtube.nl/assets/bootstrap/js/bootstrap.min.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 18 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://youngtube.nl/
Allowed
http://youngtube.nl/assets/web/assets/mobirise-icons/mobirise-icons.css
Allowed
http://youngtube.nl/assets/web/assets/mobirise-icons2/mobirise2.css
Allowed
http://youngtube.nl/assets/bootstrap/css/bootstrap.min.css
Allowed
http://youngtube.nl/assets/bootstrap/css/bootstrap-grid.min.css
Allowed
http://youngtube.nl/assets/bootstrap/css/bootstrap-reboot.min.css
Allowed
http://youngtube.nl/assets/tether/tether.min.css
Allowed
http://youngtube.nl/assets/theme/css/style.css
Allowed
http://youngtube.nl/assets/mobirise/css/mbr-additional.css
Allowed
http://youngtube.nl/assets/web/assets/jquery/jquery.min.js
Allowed
http://youngtube.nl/assets/popper/popper.min.js
Allowed
http://youngtube.nl/assets/bootstrap/js/bootstrap.min.js
Allowed
http://youngtube.nl/assets/tether/tether.min.js
Allowed
http://youngtube.nl/assets/smoothscroll/smooth-scroll.js
Allowed
http://youngtube.nl/assets/parallax/jarallax.min.js
Allowed
http://youngtube.nl/assets/theme/js/script.js
Allowed
http://youngtube.nl/assets/formoid/formoid.min.js
Allowed
http://youngtube.nl/assets/images/mbr-1920x1279.jpg
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
1
Medium
4
Medium
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for youngtube.nl. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of youngtube.nl on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Crawling and Indexing

robots.txt is not valid — Request for robots.txt returned HTTP status: 500
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
30

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of youngtube.nl. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of youngtube.nl on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 185.104.29.70
Continent: Europe
Country: Netherlands
Netherlands Flag
Region:
City:
Longitude: 4.8995
Latitude: 52.3824
Currencies: EUR
Languages: Dutch

Web Hosting Provider

Name IP Address
VIMEXX
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Technical

DNS Lookup

NS Records

Host Nameserver Class TTL
youngtube.nl. nsn1.mijndomein.nl. IN 21600
youngtube.nl. nsn2.mijndomein.nl. IN 21600
youngtube.nl. nsn3.mijndomein.nl. IN 21600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
date: 2nd March, 2023
server: Apache/2
cache-control: max-age=0
expires: 2nd March, 2023
content-type: text/html; charset=UTF-8
x-powered-by: PHP/7.0.33
upgrade: h2,h2c
connection: Upgrade
vary: User-Agent

Whois Lookup

Created: 28th October, 2018
Changed: 12th May, 2020
Expires:
Registrar: Metaregistrar B.V.
Zuidelijk Halfrond 1
2801DD Gouda
Netherlands
Abuse Contact:
+31.858885692
abuse@metaregistrar.com
Creation Date: 2018-10-28
Updated Date: 2020-12-05
DNSSEC: yes
Status:
Nameservers: nsn1.mijndomein.nl
nsn2.mijndomein.nl
nsn3.mijndomein.nl
Full Whois: Domain name: youngtube.nl
Status: active

Reseller:
Mijndomein Hosting BV
Albert Einsteinweg 4
8218NH Lelystad
Netherlands

Registrar:
Metaregistrar B.V.
Zuidelijk Halfrond 1
2801DD Gouda
Netherlands

Abuse Contact:
+31.858885692
abuse@metaregistrar.com

Creation Date: 2018-10-28

Updated Date: 2020-12-05

DNSSEC: yes

Domain nameservers:
nsn1.mijndomein.nl
nsn2.mijndomein.nl
nsn3.mijndomein.nl

Record maintained by: NL Domain Registry

Copyright notice
No part of this publication may be reproduced, published, stored in a
retrieval system, or transmitted, in any form or by any means,
electronic, mechanical, recording, or otherwise, without prior
permission of the Foundation for Internet Domain Registration in the
Netherlands (SIDN).
These restrictions apply equally to registrars, except in that
reproductions and publications are permitted insofar as they are
reasonable, necessary and solely in the context of the registration
activities referred to in the General Terms and Conditions for .nl
Registrars.
Any use of this material for advertising, targeting commercial offers or
similar activities is explicitly forbidden and liable to result in legal
action. Anyone who is aware or suspects that such activities are taking
place is asked to inform the Foundation for Internet Domain Registration
in the Netherlands.
(c) The Foundation for Internet Domain Registration in the Netherlands
(SIDN) Dutch Copyright Act, protection of authors' rights (Section 10,
subsection 1, clause 1).

Nameservers

Name IP Address
nsn1.mijndomein.nl 192.174.68.15
nsn2.mijndomein.nl 176.97.158.15
nsn3.mijndomein.nl 156.154.66.107
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$279 USD 1/5
0/5
0/5