Report Summary

  • 79

    Performance

    Renders faster than
    86% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

skutsjehistorie.nl

Skutsjehistorie

Page Load Speed

1.6 sec in total

First Response

348 ms

Resources Loaded

1.2 sec

Page Rendered

112 ms

skutsjehistorie.nl screenshot

About Website

Click here to check amazing Skutsjehistorie content. Otherwise, check out these important facts you probably never knew about skutsjehistorie.nl

De Stichting Foar de Neiteam archiveert, documenteert en verbreidt kennis over het skûtsjesilen, het wedstrijdzeilen met antieke vrachtschepen in Friesland.

Visit skutsjehistorie.nl

Key Findings

We analyzed Skutsjehistorie.nl page load time and found that the first response time was 348 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

skutsjehistorie.nl performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

skutsjehistorie.nl

348 ms

style2.css

162 ms

home2.css

167 ms

jquery-1.11.1.min.js

501 ms

algscr2.js

170 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 94% of them (31 requests) were addressed to the original Skutsjehistorie.nl, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (501 ms) belongs to the original domain Skutsjehistorie.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 146.6 kB (44%)

Content Size

332.1 kB

After Optimization

185.5 kB

In fact, the total size of Skutsjehistorie.nl main page is 332.1 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. 25% of websites need less resources to load. Javascripts take 156.9 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 35.6 kB

  • Original 40.0 kB
  • After minification 37.1 kB
  • After compression 4.4 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 35.6 kB or 89% of the original size.

Image Optimization

-6%

Potential reduce by 7.0 kB

  • Original 126.8 kB
  • After minification 119.8 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. Skutsjehistorie images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 97.4 kB

  • Original 156.9 kB
  • After minification 146.3 kB
  • After compression 59.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 97.4 kB or 62% of the original size.

CSS Optimization

-79%

Potential reduce by 6.6 kB

  • Original 8.3 kB
  • After minification 6.3 kB
  • After compression 1.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. Skutsjehistorie.nl needs all CSS files to be minified and compressed as it can save up to 6.6 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (17%)

Requests Now

30

After Optimization

25

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

Accessibility Review

skutsjehistorie.nl accessibility score

100

Accessibility Issues

Best Practices

skutsjehistorie.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

skutsjehistorie.nl SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Skutsjehistorie.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 Skutsjehistorie.nl main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Skutsjehistorie. 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: