Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

stadeoceane.com

Stade Océane Le Havre – Faites le plein d'énergie positive

Page Load Speed

6.1 sec in total

First Response

1.9 sec

Resources Loaded

3.7 sec

Page Rendered

492 ms

stadeoceane.com screenshot

About Website

Welcome to stadeoceane.com homepage info - get ready to check Stade Oceane best content right away, or after learning these important things about stadeoceane.com

Le Stade Océane situé au Havre est un stade multifonction disposant de 25 000 places assises en configuration football, et jusqu’à 28000 spectateurs en mode spectacle.

Visit stadeoceane.com

Key Findings

We analyzed Stadeoceane.com page load time and found that the first response time was 1.9 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

stadeoceane.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

stadeoceane.com

1914 ms

style.min.css

155 ms

style.css

233 ms

bulma.css

329 ms

hamburgers.css

260 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 55% of them (42 requests) were addressed to the original Stadeoceane.com, 22% (17 requests) were made to Static.xx.fbcdn.net and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Stadeoceane.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 417.4 kB (17%)

Content Size

2.4 MB

After Optimization

2.0 MB

In fact, the total size of Stadeoceane.com main page is 2.4 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. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 76.6 kB

  • Original 95.9 kB
  • After minification 89.2 kB
  • After compression 19.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 76.6 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 12.3 kB

  • Original 1.6 MB
  • After minification 1.6 MB

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. Stade Oceane images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 323.6 kB

  • Original 676.9 kB
  • After minification 676.9 kB
  • After compression 353.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 323.6 kB or 48% of the original size.

CSS Optimization

-5%

Potential reduce by 4.9 kB

  • Original 89.6 kB
  • After minification 89.4 kB
  • After compression 84.7 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. Stadeoceane.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 54 (78%)

Requests Now

69

After Optimization

15

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

Accessibility Review

stadeoceane.com accessibility score

100

Accessibility Issues

Best Practices

stadeoceane.com best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

stadeoceane.com 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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stadeoceane.com 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 Stadeoceane.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 Stade Oceane. 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: