Tools & Wizards About Us
amstel-klokkenmaker.nl screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

amstel-klokkenmaker.nl

Amstel-Klokkenmaker Amstelveen: voor vakkundige reparaties

Page Load Speed

6.2 sec in total

First Response

291 ms

Resources Loaded

5.8 sec

Page Rendered

145 ms

amstel-klokkenmaker.nl screenshot

About Website

Welcome to amstel-klokkenmaker.nl homepage info - get ready to check Amstel Klokkenmaker best content right away, or after learning these important things about amstel-klokkenmaker.nl

Gespecialiseerd in onderhoud, reparatie en restauratie van alle soorten antieke, klassieke en elektrische klokken. Vakmanschap en een hoog serviceniveau!

Visit amstel-klokkenmaker.nl

Key Findings

We analyzed Amstel-klokkenmaker.nl page load time and found that the first response time was 291 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

amstel-klokkenmaker.nl performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.497

16/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

amstel-klokkenmaker.nl

291 ms

amstel-klokkenmaker.nl

2306 ms

styles.css

100 ms

woocommerce-layout.css

199 ms

woocommerce.css

469 ms

Our browser made a total of 157 requests to load all elements on the main page. We found that 94% of them (148 requests) were addressed to the original Amstel-klokkenmaker.nl, 4% (6 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Amstel-klokkenmaker.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.5 MB (76%)

Content Size

4.6 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Amstel-klokkenmaker.nl main page is 4.6 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. 70% of websites need less resources to load. Javascripts take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 107.6 kB

  • Original 135.3 kB
  • After minification 131.4 kB
  • After compression 27.8 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 107.6 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 1.0 kB

  • Original 102.6 kB
  • After minification 101.6 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. Amstel Klokkenmaker images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 1.9 MB

  • Original 2.6 MB
  • After minification 2.4 MB
  • After compression 732.2 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 1.9 MB or 72% of the original size.

CSS Optimization

-86%

Potential reduce by 1.5 MB

  • Original 1.8 MB
  • After minification 1.6 MB
  • After compression 239.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. Amstel-klokkenmaker.nl needs all CSS files to be minified and compressed as it can save up to 1.5 MB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 142 (95%)

Requests Now

149

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

amstel-klokkenmaker.nl

amstel-klokkenmaker.nl

291 ms

amstel-klokkenmaker.nl

amstel-klokkenmaker.nl

2306 ms

styles.css

styles.css

100 ms

woocommerce-layout.css

woocommerce-layout.css

199 ms

woocommerce.css

woocommerce.css

469 ms

cookieblocker.min.css

cookieblocker.min.css

286 ms

header-footer-elementor.css

header-footer-elementor.css

286 ms

frontend-lite.min.css

frontend-lite.min.css

560 ms

swiper.min.css

swiper.min.css

378 ms

post-8.css

post-8.css

298 ms

global.css

global.css

474 ms

post-75495.css

post-75495.css

383 ms

frontend.css

frontend.css

487 ms

post-78191.css

post-78191.css

476 ms

post-81369.css

post-81369.css

480 ms

flaticon.css

flaticon.css

565 ms

headding-title.css

headding-title.css

573 ms

rsaddons.css

rsaddons.css

574 ms

heading.css

heading.css

583 ms

animated-heading.css

animated-heading.css

583 ms

team-slider-widget.css

team-slider-widget.css

663 ms

portfolio-slider.css

portfolio-slider.css

671 ms

counter.css

counter.css

680 ms

rs-service-grid.css

rs-service-grid.css

681 ms

service-slider-widget.css

service-slider-widget.css

756 ms

rs-video.css

rs-video.css

761 ms

pricing-table.css

pricing-table.css

767 ms

rs-pricing-table.css

rs-pricing-table.css

767 ms

button.css

button.css

779 ms

logo-widget.css

logo-widget.css

780 ms

cta.css

cta.css

856 ms

testimonail-widget.css

testimonail-widget.css

860 ms

testimonail-slider-widget.css

testimonail-slider-widget.css

865 ms

css

css

67 ms

css

css

84 ms

css

css

100 ms

advanced-tab.css

advanced-tab.css

873 ms

iconbox.css

iconbox.css

863 ms

blog-grid.css

blog-grid.css

764 ms

number.css

number.css

684 ms

cf7.css

cf7.css

683 ms

rs-progress.css

rs-progress.css

684 ms

contact-box.css

contact-box.css

604 ms

rs-tooltip.css

rs-tooltip.css

678 ms

static-product.css

static-product.css

588 ms

image-widget.css

image-widget.css

592 ms

image-hover-widget.css

image-hover-widget.css

592 ms

feature-list.css

feature-list.css

599 ms

dual-button.css

dual-button.css

589 ms

image-animation.css

image-animation.css

594 ms

breadcrumb-widget.css

breadcrumb-widget.css

592 ms

accordion.css

accordion.css

589 ms

apps-screenshots.css

apps-screenshots.css

598 ms

rs-roadmap.css

rs-roadmap.css

596 ms

event-grid.css

event-grid.css

598 ms

marquee-slider-widget.css

marquee-slider-widget.css

594 ms

bootstrap.min.css

bootstrap.min.css

777 ms

remixicon.css

remixicon.css

696 ms

owl.carousel.css

owl.carousel.css

599 ms

slick.css

slick.css

597 ms

magnific-popup.css

magnific-popup.css

592 ms

swiper.min.css

swiper.min.css

592 ms

default.css

default.css

981 ms

rsanimations.css

rsanimations.css

674 ms

responsive.css

responsive.css

856 ms

style.css

style.css

602 ms

wc-blocks.css

wc-blocks.css

613 ms

rs6.css

rs6.css

680 ms

jquery.min.js

jquery.min.js

689 ms

jquery-migrate.min.js

jquery-migrate.min.js

679 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

696 ms

js.cookie.min.js

js.cookie.min.js

687 ms

woocommerce.min.js

woocommerce.min.js

698 ms

index.js

index.js

692 ms

index.js

index.js

707 ms

rbtools.min.js

rbtools.min.js

849 ms

rs6.min.js

rs6.min.js

952 ms

sourcebuster.min.js

sourcebuster.min.js

756 ms

order-attribution.min.js

order-attribution.min.js

755 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

750 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

841 ms

wp-polyfill.min.js

wp-polyfill.min.js

832 ms

react.min.js

react.min.js

832 ms

hooks.min.js

hooks.min.js

755 ms

deprecated.min.js

deprecated.min.js

775 ms

dom.min.js

dom.min.js

827 ms

react-dom.min.js

react-dom.min.js

1009 ms

escape-html.min.js

escape-html.min.js

814 ms

element.min.js

element.min.js

812 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

769 ms

i18n.min.js

i18n.min.js

770 ms

keycodes.min.js

keycodes.min.js

827 ms

priority-queue.min.js

priority-queue.min.js

809 ms

compose.min.js

compose.min.js

737 ms

private-apis.min.js

private-apis.min.js

767 ms

redux-routine.min.js

redux-routine.min.js

763 ms

data.min.js

data.min.js

803 ms

lodash.min.js

lodash.min.js

733 ms

wc-blocks-registry.js

wc-blocks-registry.js

740 ms

url.min.js

url.min.js

757 ms

api-fetch.min.js

api-fetch.min.js

744 ms

wc-settings.js

wc-settings.js

726 ms

data-controls.min.js

data-controls.min.js

727 ms

html-entities.min.js

html-entities.min.js

726 ms

notices.min.js

notices.min.js

710 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

676 ms

wc-blocks-data.js

wc-blocks-data.js

676 ms

dom-ready.min.js

dom-ready.min.js

712 ms

a11y.min.js

a11y.min.js

722 ms

primitives.min.js

primitives.min.js

706 ms

warning.min.js

warning.min.js

573 ms

blocks-components.js

blocks-components.js

603 ms

blocks-checkout.js

blocks-checkout.js

605 ms

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuJJmJxAct.ttf

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuJJmJxAct.ttf

28 ms

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuFpmJxAct.ttf

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuFpmJxAct.ttf

55 ms

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuyJ6JxAct.ttf

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuyJ6JxAct.ttf

109 ms

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymu8Z6JxAct.ttf

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymu8Z6JxAct.ttf

96 ms

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymulp6JxAct.ttf

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymulp6JxAct.ttf

108 ms

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuv56JxAct.ttf

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuv56JxAct.ttf

242 ms

order-attribution-blocks.min.js

order-attribution-blocks.min.js

651 ms

popper.min.js

popper.min.js

648 ms

headding-title.js

headding-title.js

570 ms

slick.min.js

slick.min.js

574 ms

tilt.jquery.min.js

tilt.jquery.min.js

609 ms

jquery-ui.js

jquery-ui.js

699 ms

parallax-effect.min.js

parallax-effect.min.js

634 ms

jQuery-plugin-progressbar.js

jQuery-plugin-progressbar.js

638 ms

imagesloaded.min.js

imagesloaded.min.js

584 ms

custom.js

custom.js

590 ms

jquery.marquee.min.js

jquery.marquee.min.js

638 ms

modernizr-2.8.3.min.js

modernizr-2.8.3.min.js

641 ms

bootstrap.min.js

bootstrap.min.js

712 ms

owl.carousel.min.js

owl.carousel.min.js

651 ms

classie.js

classie.js

654 ms

swiper.min.js

swiper.min.js

653 ms

waypoints.min.js

waypoints.min.js

622 ms

waypoints-sticky.min.js

waypoints-sticky.min.js

637 ms

jquery.counterup.min.js

jquery.counterup.min.js

593 ms

isotope.js

isotope.js

587 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

582 ms

main.js

main.js

612 ms

complianz.min.js

complianz.min.js

595 ms

frontend.js

frontend.js

638 ms

webpack.runtime.min.js

webpack.runtime.min.js

602 ms

frontend-modules.min.js

frontend-modules.min.js

590 ms

waypoints.min.js

waypoints.min.js

591 ms

core.min.js

core.min.js

622 ms

frontend.min.js

frontend.min.js

593 ms

underscore.min.js

underscore.min.js

637 ms

wp-util.min.js

wp-util.min.js

603 ms

frontend.min.js

frontend.min.js

593 ms

faviklok.png

faviklok.png

591 ms

cropped-amstel-klokkenmaker.png

cropped-amstel-klokkenmaker.png

621 ms

dummy.png

dummy.png

594 ms

klokkenmaker-700KB-696x1024-1-qgeyap4qppciu2g8903tgn4r0uvzuaxkvcqhx0o1k0.jpg

klokkenmaker-700KB-696x1024-1-qgeyap4qppciu2g8903tgn4r0uvzuaxkvcqhx0o1k0.jpg

639 ms

black-img.jpg

black-img.jpg

602 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

100 ms

Accessibility Review

amstel-klokkenmaker.nl accessibility score

88

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

[aria-*] attributes do not match their roles

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.

Best Practices

amstel-klokkenmaker.nl best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

amstel-klokkenmaker.nl SEO score

93

Search Engine Optimization Advices

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 Amstel-klokkenmaker.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 Amstel-klokkenmaker.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

amstel-klokkenmaker.nl

Open Graph data is detected on the main page of Amstel Klokkenmaker. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: