Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

sokos.fi

Sokos verkkokauppa

Page Load Speed

10.1 sec in total

First Response

566 ms

Resources Loaded

8.8 sec

Page Rendered

652 ms

sokos.fi screenshot

About Website

Welcome to sokos.fi homepage info - get ready to check Sokos best content for Finland right away, or after learning these important things about sokos.fi

Sokos verkkokauppa -- Valikoimassa on yli 40 000 tuotetta.

Visit sokos.fi

Key Findings

We analyzed Sokos.fi page load time and found that the first response time was 566 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize Sokos.fi rating and web reputation

Performance Metrics

sokos.fi performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value19.4 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value7,300 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.596

11/100

15%

TTI (Time to Interactive)

Value26.7 s

0/100

10%

Network Requests Diagram

www.sokos.fi

566 ms

sokos

572 ms

dojo.js

550 ms

css

62 ms

idangerous.swiper.css

335 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 63% of them (60 requests) were addressed to the original Sokos.fi, 4% (4 requests) were made to Connect.nosto.com and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Mugmiddlewear.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (50%)

Content Size

4.2 MB

After Optimization

2.1 MB

In fact, the total size of Sokos.fi main page is 4.2 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. 60% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 586.8 kB

  • Original 664.8 kB
  • After minification 508.3 kB
  • After compression 78.0 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. This page needs HTML code to be minified as it can gain 156.4 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 586.8 kB or 88% of the original size.

Image Optimization

-3%

Potential reduce by 45.1 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. Sokos images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 1.2 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 408.0 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 1.2 MB or 75% of the original size.

CSS Optimization

-83%

Potential reduce by 268.7 kB

  • Original 324.0 kB
  • After minification 321.5 kB
  • After compression 55.4 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. Sokos.fi needs all CSS files to be minified and compressed as it can save up to 268.7 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

87

After Optimization

56

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

Accessibility Review

sokos.fi accessibility score

64

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA IDs are not unique

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

sokos.fi best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

sokos.fi SEO score

82

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Encoding

    UTF-8

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