Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

ouderwetsewinkel.nl

Boom | Ouderwetsewinkel.nl - De klompen, borstel en touw specialist

Page Load Speed

3.4 sec in total

First Response

717 ms

Resources Loaded

2.4 sec

Page Rendered

248 ms

ouderwetsewinkel.nl screenshot

About Website

Welcome to ouderwetsewinkel.nl homepage info - get ready to check Ouderwetsewinkel best content right away, or after learning these important things about ouderwetsewinkel.nl

Klompen, borstels, huishoudelijke artikelen & touw. En dat sinds 1835. U vindt in mijn webshop en winkel in Alkmaar die leuke ouderwetse producten die nergens anders meer te koop zijn!

Visit ouderwetsewinkel.nl

Key Findings

We analyzed Ouderwetsewinkel.nl page load time and found that the first response time was 717 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

ouderwetsewinkel.nl performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

www.ouderwetsewinkel.nl

717 ms

07e8f34f75cdc3c80a6a32005dae29b5.css

332 ms

7f11b1f50a2550dcbaabefe8dbedd751.js

750 ms

geschuurd-rondneus-06_2.png

96 ms

eigentekst_1.png

97 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 90% of them (19 requests) were addressed to the original Ouderwetsewinkel.nl, 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (750 ms) belongs to the original domain Ouderwetsewinkel.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 498.1 kB (60%)

Content Size

835.3 kB

After Optimization

337.2 kB

In fact, the total size of Ouderwetsewinkel.nl main page is 835.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 397.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 24.9 kB

  • Original 31.4 kB
  • After minification 27.8 kB
  • After compression 6.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 3.6 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 24.9 kB or 79% of the original size.

Image Optimization

-31%

Potential reduce by 104.2 kB

  • Original 336.7 kB
  • After minification 232.5 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Ouderwetsewinkel needs image optimization as it can save up to 104.2 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-78%

Potential reduce by 309.3 kB

  • Original 397.7 kB
  • After minification 300.4 kB
  • After compression 88.5 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 309.3 kB or 78% of the original size.

CSS Optimization

-86%

Potential reduce by 59.7 kB

  • Original 69.4 kB
  • After minification 49.5 kB
  • After compression 9.8 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Ouderwetsewinkel.nl needs all CSS files to be minified and compressed as it can save up to 59.7 kB or 86% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

20

After Optimization

20

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ouderwetsewinkel. According to our analytics all requests are already optimized.

Accessibility Review

ouderwetsewinkel.nl accessibility score

79

Accessibility Issues

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.

Impact

Issue

High

[role]s do not have all required [aria-*] attributes

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

ouderwetsewinkel.nl best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ouderwetsewinkel.nl SEO score

79

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ouderwetsewinkel.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Ouderwetsewinkel.nl main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Ouderwetsewinkel. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: