Goplay.be Site Title
GoPlay | Kijk online naar volledige afleveringen
Goplay.be Meta Description
Bekijk volledige afleveringen van onze programma's op GoPlay.
Goplay.be Test Results
Goplay.be Mobile Performance: 15/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript. Potential savings of 753 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Avoid multiple page redirects. Potential savings of 3,450 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Eliminate render-blocking resources. Potential savings of 1,700 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Remove unused CSS. Potential savings of 57 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Reduce the impact of third-party code
Third-party code blocked the main thread for 320 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Serve static assets with an efficient cache policy
22 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
9.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
5.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid an excessive DOM size
1,365 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Avoid chaining critical requests
8 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Keep request counts low and transfer sizes small
56 requests • 1,958 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Goplay.be Mobile SEO: 92/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Goplay.be Mobile Best Practices: 71/100
Quick overview:
Trust and Safety
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn More
Goplay.be Mobile Progressive Web App: 25/100
Quick overview:
PWA Optimized
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Installable
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Fast and reliable
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Page load is not fast enough on mobile networks
Interactive at 17.4 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
Goplay.be Mobile Accessibility: 78/100
Quick overview:
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[aria-*]` attributes are not valid or misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Similar sites
Similar tests
www.goplay.com
www.goplay.net
www.goplay.org
www.goplay.info
www.goplay.biz
www.goplay.us
www.goplay.mobi
www.oplay.be
www.goplay.be
www.foplay.be
www.gfoplay.be
www.fgoplay.be
www.voplay.be
www.gvoplay.be
www.vgoplay.be
www.toplay.be
www.gtoplay.be
www.tgoplay.be
www.boplay.be
www.gboplay.be
www.bgoplay.be
www.yoplay.be
www.gyoplay.be
www.ygoplay.be
www.hoplay.be
www.ghoplay.be
www.hgoplay.be
www.gplay.be
www.giplay.be
www.goiplay.be
www.gioplay.be
www.gkplay.be
www.gokplay.be
www.gkoplay.be
www.glplay.be
www.golplay.be
www.gloplay.be
www.gpplay.be
www.gopplay.be
www.gpoplay.be
www.golay.be
www.goolay.be
www.gopolay.be
www.gooplay.be
www.gollay.be
www.gopllay.be
www.gopay.be
www.goppay.be
www.goplpay.be
www.gopoay.be
www.goploay.be
www.gopkay.be
www.goplkay.be
www.gopklay.be
www.goply.be
www.goplqy.be
www.goplaqy.be
www.goplqay.be
www.goplwy.be
www.goplawy.be
www.goplway.be
www.goplsy.be
www.goplasy.be
www.goplsay.be
www.goplzy.be
www.goplazy.be
www.goplzay.be
www.gopla.be
www.goplat.be
www.goplayt.be
www.goplaty.be
www.goplag.be
www.goplayg.be
www.goplagy.be
www.goplah.be
www.goplayh.be
www.goplahy.be
www.goplau.be
www.goplayu.be
www.goplauy.be
www.goplay.net
www.goplay.org
www.goplay.info
www.goplay.biz
www.goplay.us
www.goplay.mobi
www.oplay.be
www.goplay.be
www.foplay.be
www.gfoplay.be
www.fgoplay.be
www.voplay.be
www.gvoplay.be
www.vgoplay.be
www.toplay.be
www.gtoplay.be
www.tgoplay.be
www.boplay.be
www.gboplay.be
www.bgoplay.be
www.yoplay.be
www.gyoplay.be
www.ygoplay.be
www.hoplay.be
www.ghoplay.be
www.hgoplay.be
www.gplay.be
www.giplay.be
www.goiplay.be
www.gioplay.be
www.gkplay.be
www.gokplay.be
www.gkoplay.be
www.glplay.be
www.golplay.be
www.gloplay.be
www.gpplay.be
www.gopplay.be
www.gpoplay.be
www.golay.be
www.goolay.be
www.gopolay.be
www.gooplay.be
www.gollay.be
www.gopllay.be
www.gopay.be
www.goppay.be
www.goplpay.be
www.gopoay.be
www.goploay.be
www.gopkay.be
www.goplkay.be
www.gopklay.be
www.goply.be
www.goplqy.be
www.goplaqy.be
www.goplqay.be
www.goplwy.be
www.goplawy.be
www.goplway.be
www.goplsy.be
www.goplasy.be
www.goplsay.be
www.goplzy.be
www.goplazy.be
www.goplzay.be
www.gopla.be
www.goplat.be
www.goplayt.be
www.goplaty.be
www.goplag.be
www.goplayg.be
www.goplagy.be
www.goplah.be
www.goplayh.be
www.goplahy.be
www.goplau.be
www.goplayu.be
www.goplauy.be