Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

egmont.fi

Sarjakuvien ja lastentuotteiden kustantamo - Story House Egmont

Page Load Speed

5.1 sec in total

First Response

370 ms

Resources Loaded

3.9 sec

Page Rendered

889 ms

egmont.fi screenshot

About Website

Welcome to egmont.fi homepage info - get ready to check Egmont best content right away, or after learning these important things about egmont.fi

Story House Egmont julkaisee sarjakuva-, lasten-, urheilu- ja harrastelehtiä, sarjakuva- ja lastenkirjoja sekä puuha- ja värityskirjoja.

Visit egmont.fi

Key Findings

We analyzed Egmont.fi page load time and found that the first response time was 370 ms and then it took 4.8 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

egmont.fi performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.159

73/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

egmont.fi

370 ms

egmont.fi

449 ms

storyhouseegmont.fi

679 ms

uc.js

109 ms

font-awesome.min.css

115 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Egmont.fi, 86% (72 requests) were made to Storyhouseegmont.fi and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Storyhouseegmont.fi.

Page Optimization Overview & Recommendations

Page size can be reduced by 92.4 kB (3%)

Content Size

3.4 MB

After Optimization

3.3 MB

In fact, the total size of Egmont.fi main page is 3.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. 65% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 92.3 kB

  • Original 109.7 kB
  • After minification 103.0 kB
  • After compression 17.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 92.3 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 14 B

  • Original 3.2 MB
  • After minification 3.2 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. Egmont images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 87 B

  • Original 34.9 kB
  • After minification 34.9 kB
  • After compression 34.8 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.

Requests Breakdown

Number of requests can be reduced by 42 (53%)

Requests Now

80

After Optimization

38

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

Accessibility Review

egmont.fi accessibility score

83

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

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

egmont.fi best practices score

83

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

Browser errors were logged to the console

SEO Factors

egmont.fi SEO score

97

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FI

  • Language Claimed

    FI

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Egmont.fi can be misinterpreted by Google and other search engines. Our service has detected that Finnish is used on the page, and it matches the claimed language. Our system also found out that Egmont.fi 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 data is detected on the main page of Egmont. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: