Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

amsterdamer.fr

Votre blog 100% vélo & VAE | Amsterdamer

Page Load Speed

3.6 sec in total

First Response

846 ms

Resources Loaded

2.4 sec

Page Rendered

333 ms

amsterdamer.fr screenshot

About Website

Welcome to amsterdamer.fr homepage info - get ready to check Amsterdamer best content for France right away, or after learning these important things about amsterdamer.fr

Amoureux du deux roues ? Rejoignez-nous ! On partage des conseils pratiques, des histoires de route et des avis sur l'équipement.

Visit amsterdamer.fr

Key Findings

We analyzed Amsterdamer.fr page load time and found that the first response time was 846 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

amsterdamer.fr performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value1,390 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value25.6 s

0/100

10%

Network Requests Diagram

www.amsterdamer.fr

846 ms

shared.css

270 ms

bootstrap-grid.css

182 ms

style.css

277 ms

jquery-1.6.1.min.js

363 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 83% of them (63 requests) were addressed to the original Amsterdamer.fr, 8% (6 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (846 ms) belongs to the original domain Amsterdamer.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 486.5 kB (38%)

Content Size

1.3 MB

After Optimization

783.4 kB

In fact, the total size of Amsterdamer.fr main page is 1.3 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. Images take 633.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 79.2 kB

  • Original 95.5 kB
  • After minification 94.5 kB
  • After compression 16.3 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 79.2 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 27.6 kB

  • Original 633.3 kB
  • After minification 605.7 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. Amsterdamer images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 304.1 kB

  • Original 450.4 kB
  • After minification 434.1 kB
  • After compression 146.3 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 304.1 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 75.6 kB

  • Original 90.7 kB
  • After minification 71.3 kB
  • After compression 15.1 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. Amsterdamer.fr needs all CSS files to be minified and compressed as it can save up to 75.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (36%)

Requests Now

72

After Optimization

46

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

Accessibility Review

amsterdamer.fr accessibility score

90

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.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

amsterdamer.fr best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

amsterdamer.fr SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    FR

  • Language Claimed

    FR

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amsterdamer.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Amsterdamer.fr 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 Amsterdamer. 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: