Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

therdershof.be

Honden en kattenhotel - Trimsalon - Hondenbegeleiding | tHERDERSHOF menu

Page Load Speed

2.4 sec in total

First Response

146 ms

Resources Loaded

2.2 sec

Page Rendered

70 ms

therdershof.be screenshot

About Website

Click here to check amazing THERDERSHOF content. Otherwise, check out these important facts you probably never knew about therdershof.be

In t'Herdershof doen we er alles aan om je trouwe vriend een echt thuisgevoel te geven. Kleine honden die liever in een huiselijke sfeer vertoeven, verwelkomen we in ons hondenhotel.

Visit therdershof.be

Key Findings

We analyzed Therdershof.be page load time and found that the first response time was 146 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

therdershof.be performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value5.4 s

57/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

www.therdershof.be

146 ms

minified.js

68 ms

focus-within-polyfill.js

66 ms

polyfill.min.js

1259 ms

thunderbolt-commons.01583709.bundle.min.js

93 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Therdershof.be, 44% (21 requests) were made to Static.parastorage.com and 25% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 540.6 kB (52%)

Content Size

1.0 MB

After Optimization

500.4 kB

In fact, the total size of Therdershof.be main page is 1.0 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. 45% of websites need less resources to load. HTML takes 507.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 398.4 kB

  • Original 507.1 kB
  • After minification 505.5 kB
  • After compression 108.7 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 398.4 kB or 79% of the original size.

Image Optimization

-24%

Potential reduce by 44.2 kB

  • Original 187.8 kB
  • After minification 143.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. Obviously, THERDERSHOF needs image optimization as it can save up to 44.2 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-28%

Potential reduce by 98.0 kB

  • Original 346.2 kB
  • After minification 346.2 kB
  • After compression 248.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 98.0 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (41%)

Requests Now

27

After Optimization

16

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

Accessibility Review

therdershof.be accessibility score

100

Accessibility Issues

Best Practices

therdershof.be best practices score

92

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

Page has valid source maps

SEO Factors

therdershof.be SEO score

98

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Therdershof.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Therdershof.be 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 THERDERSHOF. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: