Report Summary

  • 21

    Performance

    Renders faster than
    39% 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

  • 92

    SEO

    Google-friendlier than
    74% of websites

stay-in-amsterdam.com

Discovering Ghostly Legends and Lore

Page Load Speed

5.8 sec in total

First Response

651 ms

Resources Loaded

4.3 sec

Page Rendered

828 ms

stay-in-amsterdam.com screenshot

About Website

Click here to check amazing Stay In Amsterdam content. Otherwise, check out these important facts you probably never knew about stay-in-amsterdam.com

Visit stay-in-amsterdam.com

Key Findings

We analyzed Stay-in-amsterdam.com page load time and found that the first response time was 651 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

stay-in-amsterdam.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value1,310 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

www.stay-in-amsterdam.com

651 ms

style.min.css

381 ms

wpautoterms.css

159 ms

styles.css

165 ms

fontfaces.css

325 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 49% of them (29 requests) were addressed to the original Stay-in-amsterdam.com, 20% (12 requests) were made to Fonts.gstatic.com and 15% (9 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (934 ms) relates to the external source Youtube.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 649.9 kB (35%)

Content Size

1.9 MB

After Optimization

1.2 MB

In fact, the total size of Stay-in-amsterdam.com main page is 1.9 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. Only a small number of websites need less resources to load. Images take 844.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 91.7 kB

  • Original 116.6 kB
  • After minification 112.7 kB
  • After compression 24.9 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 91.7 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 7.5 kB

  • Original 844.1 kB
  • After minification 836.5 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. Stay In Amsterdam images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 221.1 kB

  • Original 481.6 kB
  • After minification 471.9 kB
  • After compression 260.6 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 221.1 kB or 46% of the original size.

CSS Optimization

-75%

Potential reduce by 329.7 kB

  • Original 439.4 kB
  • After minification 384.3 kB
  • After compression 109.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. Stay-in-amsterdam.com needs all CSS files to be minified and compressed as it can save up to 329.7 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (51%)

Requests Now

45

After Optimization

22

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

Accessibility Review

stay-in-amsterdam.com accessibility score

100

Accessibility Issues

Best Practices

stay-in-amsterdam.com 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

stay-in-amsterdam.com SEO score

92

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stay-in-amsterdam.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Stay-in-amsterdam.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 description is not detected on the main page of Stay In Amsterdam. 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: