Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

dijkshoorn.com

Uw dierenarts in Zeist | Dierenkliniek Dijkshoorn

Page Load Speed

2.9 sec in total

First Response

223 ms

Resources Loaded

2.6 sec

Page Rendered

80 ms

About Website

Welcome to dijkshoorn.com homepage info - get ready to check Dijkshoorn best content right away, or after learning these important things about dijkshoorn.com

Welkom bij Dierenkliniek Dijkshoorn! U kunt bij ons terecht voor o.a. vaccinaties, knieoperaties en doofheidsonderzoeken.

Visit dijkshoorn.com

Key Findings

We analyzed Dijkshoorn.com page load time and found that the first response time was 223 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

dijkshoorn.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

2/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value390 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.5 s

48/100

10%

Network Requests Diagram

dijkshoorn.com

223 ms

dijkshoorn.com

359 ms

www.dijkshoorn.com

504 ms

nl-nl

377 ms

ai.0.js

16 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 71% of them (15 requests) were addressed to the original Dijkshoorn.com, 10% (2 requests) were made to Weu-az-web-nl-uat-cdnep.azureedge.net and 5% (1 request) were made to Az416426.vo.msecnd.net. The less responsive or slowest element that took the longest time to load (707 ms) relates to the external source Weu-az-web-nl-uat-cdnep.azureedge.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 46.1 kB (17%)

Content Size

269.0 kB

After Optimization

222.9 kB

In fact, the total size of Dijkshoorn.com main page is 269.0 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. 35% of websites need less resources to load. Javascripts take 129.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 42.2 kB

  • Original 53.3 kB
  • After minification 47.8 kB
  • After compression 11.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. 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 42.2 kB or 79% of the original size.

JavaScript Optimization

-2%

Potential reduce by 2.2 kB

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

CSS Optimization

-2%

Potential reduce by 1.8 kB

  • Original 86.1 kB
  • After minification 86.1 kB
  • After compression 84.3 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. Dijkshoorn.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (57%)

Requests Now

14

After Optimization

6

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

Accessibility Review

dijkshoorn.com accessibility score

96

Accessibility Issues

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

Best Practices

dijkshoorn.com 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

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

dijkshoorn.com SEO score

100

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