Tools & Wizards About Us
thispage.amsterdam screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

thispage.amsterdam

This Page Amsterdam - Digital Agency

Page Load Speed

1.8 sec in total

First Response

187 ms

Resources Loaded

1.5 sec

Page Rendered

63 ms

thispage.amsterdam screenshot

About Website

Visit thispage.amsterdam now to see the best up-to-date This Page content for Netherlands and also check out these interesting facts you probably never knew about thispage.amsterdam

Delivering brands what they need to digitally succeed. Digital branding, design and technical realisation. Based in Amsterdam. Let's get started!

Visit thispage.amsterdam

Key Findings

We analyzed Thispage.amsterdam page load time and found that the first response time was 187 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

thispage.amsterdam performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value990 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

thispage.amsterdam

187 ms

thispage.amsterdam

772 ms

gtm.js

70 ms

app-0cdd46f0.css

90 ms

raven.min.js

36 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 35% of them (6 requests) were addressed to the original Thispage.amsterdam, 24% (4 requests) were made to Sentry.io and 6% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (772 ms) belongs to the original domain Thispage.amsterdam.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.1 kB (13%)

Content Size

264.6 kB

After Optimization

230.5 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Thispage.amsterdam main page is 264.6 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. 20% of websites need less resources to load. Javascripts take 213.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 26.8 kB

  • Original 33.6 kB
  • After minification 33.0 kB
  • After compression 6.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 26.8 kB or 80% of the original size.

JavaScript Optimization

-3%

Potential reduce by 7.3 kB

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

CSS Optimization

-0%

Potential reduce by 23 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.2 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. Thispage.amsterdam has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (60%)

Requests Now

15

After Optimization

6

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

thispage.amsterdam

thispage.amsterdam

187 ms

thispage.amsterdam

thispage.amsterdam

772 ms

gtm.js

gtm.js

70 ms

app-0cdd46f0.css

app-0cdd46f0.css

90 ms

raven.min.js

raven.min.js

36 ms

vendors-common-48e6b915.js

vendors-common-48e6b915.js

213 ms

vendors-app-a447ed1a.js

vendors-app-a447ed1a.js

347 ms

app-e373e8c7.js

app-e373e8c7.js

357 ms

4027162.js

4027162.js

101 ms

fb.js

fb.js

61 ms

banner.js

banner.js

109 ms

collectedforms.js

collectedforms.js

153 ms

4027162.js

4027162.js

220 ms

39 ms

46 ms

48 ms

36 ms

Accessibility Review

thispage.amsterdam accessibility score

94

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best Practices

thispage.amsterdam 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

thispage.amsterdam 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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thispage.amsterdam 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 Thispage.amsterdam 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

thispage.amsterdam

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