Rvi.be Site Title

Kijk en luister buiten Vlaanderen | VRT.be

Rvi.be Meta Description

Ook buiten Vlaanderen en Brussel kunt u genieten van VRT-programma's. Het VRT-aanbod is te ontvangen op verschillende platformen. In de grensgebieden en in Nederland en Wallonië zijn er nog meer opties.

Rvi.be Test Results

Rvi.be Mobile Performance: 29/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Properly size images
Potential savings of 409 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce the impact of third-party code
Third-party code blocked the main thread for 4,390 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 how to minimize third-party impact.
Reduce unused CSS
Potential savings of 73 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Defer offscreen images
Potential savings of 2,855 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Eliminate render-blocking resources
Potential savings of 1,580 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Reduce unused JavaScript
Potential savings of 1,462 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Avoid multiple page redirects
Potential savings of 1,390 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce JavaScript execution time
8.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Largest Contentful Paint element
6,730 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Some third-party resources can be lazy loaded with a facade
1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.
Minimize main-thread work
12.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Avoid serving legacy JavaScript to modern browsers
Potential savings of 28 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Serve images in next-gen formats
Potential savings of 260 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Avoid enormous network payloads
Total size was 9,300 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
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 about adopting passive event listeners.
Minify JavaScript
Potential savings of 11 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Serve static assets with an efficient cache policy
71 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Avoid an excessive DOM size
960 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Max Potential First Input Delay
1,850 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Time to Interactive
38.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
First Meaningful Paint
4.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

Rvi.be Mobile SEO: 100/100
Quick overview:

Rvi.be Mobile Best Practices: 59/100
Quick overview:
Trust and Safety
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 served over 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 about HTTPS.
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
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 about this errors in console diagnostic audit
Rvi.be Mobile Accessibility: 93/100
Quick overview:
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.
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 how to make links accessible.
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 how to provide sufficient color contrast.
Similar sites
Similar tests
www.rvi.com
www.rvi.net
www.rvi.org
www.rvi.info
www.rvi.biz
www.rvi.us
www.rvi.mobi
www.vi.be
www.rvi.be
www.evi.be
www.revi.be
www.ervi.be
www.dvi.be
www.rdvi.be
www.drvi.be
www.fvi.be
www.rfvi.be
www.frvi.be
www.tvi.be
www.rtvi.be
www.trvi.be
www.ri.be
www.rci.be
www.rvci.be
www.rcvi.be
www.rfi.be
www.rvfi.be
www.rgi.be
www.rvgi.be
www.rgvi.be
www.rbi.be
www.rvbi.be
www.rbvi.be
www.rv.be
www.rvu.be
www.rviu.be
www.rvui.be
www.rvj.be
www.rvij.be
www.rvji.be
www.rvk.be
www.rvik.be
www.rvki.be
www.rvo.be
www.rvio.be
www.rvoi.be
Last Tested: