Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

ouderwetsewinkel.nl

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

Page Load Speed

4 sec in total

First Response

464 ms

Resources Loaded

3.2 sec

Page Rendered

355 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 464 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

ouderwetsewinkel.nl performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value700 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.077

95/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

www.ouderwetsewinkel.nl

464 ms

bacb44e2481261586dc46dce59b1a851.min.css

255 ms

styles-l.min.css

342 ms

css

30 ms

logo.svg

272 ms

Our browser made a total of 148 requests to load all elements on the main page. We found that 95% of them (141 requests) were addressed to the original Ouderwetsewinkel.nl, 2% (3 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (729 ms) belongs to the original domain Ouderwetsewinkel.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 104.9 kB (9%)

Content Size

1.1 MB

After Optimization

1.0 MB

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

HTML Optimization

-86%

Potential reduce by 94.1 kB

  • Original 109.2 kB
  • After minification 96.1 kB
  • After compression 15.1 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 13.2 kB, which is 12% 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 94.1 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 8.1 kB

  • Original 725.4 kB
  • After minification 717.4 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. Ouderwetsewinkel images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.5 kB

  • Original 201.6 kB
  • After minification 201.6 kB
  • After compression 199.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 172 B

  • Original 81.1 kB
  • After minification 81.1 kB
  • After compression 80.9 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 104 (73%)

Requests Now

142

After Optimization

38

The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ouderwetsewinkel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 102 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

ouderwetsewinkel.nl accessibility score

67

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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 data is detected on the main page of Ouderwetsewinkel. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: