Fwd.nl Site Title
FWD Benelux - Living consumer electronics | FWD
Fwd.nl Meta Description
FWD.nl is dé website voor alles over consumentenelektronica. Je vindt bij ons reviews, tips, nieuws en specials over de nieuwste gadgets.
Fwd.nl Test Results
Fwd.nl Mobile Performance: 36/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Reduce initial server response time. Root document took 860 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Remove unused CSS. Potential savings of 64 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.
Remove unused JavaScript. Potential savings of 181 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Avoid serving legacy JavaScript to modern browsers. Potential savings of 19 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 More
Serve images in next-gen formats. Potential savings of 40 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Defer offscreen images. Potential savings of 46 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minimize main-thread work
4.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Serve static assets with an efficient cache policy
4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Reduce JavaScript execution time
2.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoids an excessive DOM size
740 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
User Timing marks and measures
1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. 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
Avoid large layout shifts
4 elements found
These DOM elements contribute most to the CLS of the page.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid chaining critical requests
1 chain 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
38 requests • 1,002 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Fwd.nl Mobile SEO: 90/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately
61% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
Fwd.nl Mobile Best Practices: 86/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 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.
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.
Fwd.nl Mobile Progressive Web App: 64/100
Quick overview:
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. The start_url did respond, but not via a service worker.
PWA Optimized
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.
Installable
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.
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.
Fwd.nl Mobile Accessibility: 72/100
Quick overview:
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.
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-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn more.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. 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.fwd.com
www.fwd.net
www.fwd.org
www.fwd.info
www.fwd.biz
www.fwd.us
www.fwd.mobi
www.wd.nl
www.fwd.nl
www.cwd.nl
www.fcwd.nl
www.cfwd.nl
www.dwd.nl
www.fdwd.nl
www.dfwd.nl
www.rwd.nl
www.frwd.nl
www.rfwd.nl
www.twd.nl
www.ftwd.nl
www.tfwd.nl
www.gwd.nl
www.fgwd.nl
www.gfwd.nl
www.vwd.nl
www.fvwd.nl
www.vfwd.nl
www.fd.nl
www.fqd.nl
www.fwqd.nl
www.fqwd.nl
www.fad.nl
www.fwad.nl
www.fawd.nl
www.fsd.nl
www.fwsd.nl
www.fswd.nl
www.fed.nl
www.fwed.nl
www.fewd.nl
www.fw.nl
www.fwx.nl
www.fwdx.nl
www.fwxd.nl
www.fws.nl
www.fwds.nl
www.fwe.nl
www.fwde.nl
www.fwr.nl
www.fwdr.nl
www.fwrd.nl
www.fwf.nl
www.fwdf.nl
www.fwfd.nl
www.fwc.nl
www.fwdc.nl
www.fwcd.nl
www.fwd.net
www.fwd.org
www.fwd.info
www.fwd.biz
www.fwd.us
www.fwd.mobi
www.wd.nl
www.fwd.nl
www.cwd.nl
www.fcwd.nl
www.cfwd.nl
www.dwd.nl
www.fdwd.nl
www.dfwd.nl
www.rwd.nl
www.frwd.nl
www.rfwd.nl
www.twd.nl
www.ftwd.nl
www.tfwd.nl
www.gwd.nl
www.fgwd.nl
www.gfwd.nl
www.vwd.nl
www.fvwd.nl
www.vfwd.nl
www.fd.nl
www.fqd.nl
www.fwqd.nl
www.fqwd.nl
www.fad.nl
www.fwad.nl
www.fawd.nl
www.fsd.nl
www.fwsd.nl
www.fswd.nl
www.fed.nl
www.fwed.nl
www.fewd.nl
www.fw.nl
www.fwx.nl
www.fwdx.nl
www.fwxd.nl
www.fws.nl
www.fwds.nl
www.fwe.nl
www.fwde.nl
www.fwr.nl
www.fwdr.nl
www.fwrd.nl
www.fwf.nl
www.fwdf.nl
www.fwfd.nl
www.fwc.nl
www.fwdc.nl
www.fwcd.nl