Tools & Wizards About Us
semio.fi screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

semio.fi

Semio on asiakkaan kokoinen mainostoimisto.

Page Load Speed

3.1 sec in total

First Response

315 ms

Resources Loaded

2.2 sec

Page Rendered

528 ms

semio.fi screenshot

About Website

Click here to check amazing Semio content. Otherwise, check out these important facts you probably never knew about semio.fi

Semio on mainostoimisto, joka välittää siitä miltä yrityksesi näyttää ja tuntuu. Tule katsomaan yrityksesi tulevaisuuteen.

Visit semio.fi

Key Findings

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

semio.fi performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value5.2 s

74/100

10%

Network Requests Diagram

semio.fi

315 ms

www.semio.fi

533 ms

gtm.js

68 ms

sitestyles.css

106 ms

webio2.min.site.css

207 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 90% of them (28 requests) were addressed to the original Semio.fi, 6% (2 requests) were made to Cdn.jsdelivr.net and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (953 ms) belongs to the original domain Semio.fi.

Page Optimization Overview & Recommendations

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

Content Size

1.1 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-70%

Potential reduce by 13.7 kB

  • Original 19.7 kB
  • After minification 18.5 kB
  • After compression 5.9 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 13.7 kB or 70% of the original size.

Image Optimization

-1%

Potential reduce by 12.1 kB

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

JavaScript Optimization

-1%

Potential reduce by 194 B

  • Original 38.6 kB
  • After minification 38.6 kB
  • After compression 38.4 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

-19%

Potential reduce by 3.1 kB

  • Original 15.8 kB
  • After minification 15.8 kB
  • After compression 12.8 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. Semio.fi needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (15%)

Requests Now

27

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

semio.fi

semio.fi

315 ms

www.semio.fi

www.semio.fi

533 ms

gtm.js

gtm.js

68 ms

sitestyles.css

sitestyles.css

106 ms

webio2.min.site.css

webio2.min.site.css

207 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

36 ms

webio.min.site.js

webio.min.site.js

418 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

53 ms

floatnavi.js

floatnavi.js

309 ms

jquery.nav.js

jquery.nav.js

317 ms

mainostoimisto-Semio-logo.png

mainostoimisto-Semio-logo.png

104 ms

btn-hamburger.png

btn-hamburger.png

105 ms

btn-close.png

btn-close.png

105 ms

semio-etusivu.jpg

semio-etusivu.jpg

520 ms

identiteetti-ja-ilme.png

identiteetti-ja-ilme.png

120 ms

markkinointi-ja-mainonta.png

markkinointi-ja-mainonta.png

206 ms

sivustot-ja-verkkokaupat.png

sivustot-ja-verkkokaupat.png

207 ms

viestinta.png

viestinta.png

206 ms

etusivu-perustettu.jpg

etusivu-perustettu.jpg

473 ms

nostokuva.jpg

nostokuva.jpg

517 ms

nostokuva.jpg

nostokuva.jpg

514 ms

nostokuva.jpg

nostokuva.jpg

619 ms

nostokuva.jpg

nostokuva.jpg

514 ms

footer-bg.jpg

footer-bg.jpg

953 ms

mainostoimisto-Semio-pallologo.png

mainostoimisto-Semio-pallologo.png

617 ms

fb-footericon.png

fb-footericon.png

618 ms

youtube-footericon.png

youtube-footericon.png

619 ms

instagram-footericon.png

instagram-footericon.png

622 ms

call-button.png

call-button.png

720 ms

2EAFBA_20_0.woff

2EAFBA_20_0.woff

676 ms

2EAFBA_17_0.woff

2EAFBA_17_0.woff

777 ms

Accessibility Review

semio.fi accessibility score

77

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

semio.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

SEO Factors

semio.fi SEO score

93

Search Engine Optimization Advices

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

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 Semio.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 Semio.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

semio.fi

Open Graph description is not detected on the main page of Semio. 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: