Swab.nl Site Title

Home | SWAB

Swab.nl Test Results

Swab.nl Mobile Performance: 62/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Eliminate render-blocking resources
Potential savings of 630 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.
Avoid an excessive DOM size
1,599 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.
Reduce unused JavaScript
Potential savings of 147 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.
Reduce unused CSS
Potential savings of 62 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.
Avoid multiple page redirects
Potential savings of 1,100 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Minimize main-thread work
2.2 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
Serve images in next-gen formats
Potential savings of 885 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.
Largest Contentful Paint element
8,040 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid enormous network payloads
Total size was 8,666 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
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`.
Efficiently encode images
Potential savings of 678 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Serve static assets with an efficient cache policy
24 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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.
Defer offscreen images
Potential savings of 2 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.
Max Potential First Input Delay
320 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
8.9 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.

Swab.nl Mobile SEO: 83/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
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 how to make links crawlable

Swab.nl Mobile Best Practices: 83/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.
Swab.nl Mobile Accessibility: 91/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.
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 how to make buttons more accessible.
Similar sites
Similar tests
www.swab.com
www.swab.net
www.swab.org
www.swab.info
www.swab.biz
www.swab.us
www.swab.mobi
www.wab.nl
www.swab.nl
www.wwab.nl
www.swwab.nl
www.wswab.nl
www.ewab.nl
www.sewab.nl
www.eswab.nl
www.dwab.nl
www.sdwab.nl
www.dswab.nl
www.zwab.nl
www.szwab.nl
www.zswab.nl
www.xwab.nl
www.sxwab.nl
www.xswab.nl
www.awab.nl
www.sawab.nl
www.aswab.nl
www.sab.nl
www.sqab.nl
www.swqab.nl
www.sqwab.nl
www.saab.nl
www.swaab.nl
www.ssab.nl
www.swsab.nl
www.sswab.nl
www.seab.nl
www.sweab.nl
www.swb.nl
www.swqb.nl
www.swaqb.nl
www.swwb.nl
www.swawb.nl
www.swsb.nl
www.swasb.nl
www.swzb.nl
www.swazb.nl
www.swzab.nl
www.swa.nl
www.swav.nl
www.swabv.nl
www.swavb.nl
www.swag.nl
www.swabg.nl
www.swagb.nl
www.swah.nl
www.swabh.nl
www.swahb.nl
www.swan.nl
www.swabn.nl
www.swanb.nl
Last Tested: