Tools & Wizards About Us
112.fi screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

112.fi

Hätäkeskuslaitos - Avun ja turvan ensimmäinen viranomaislenkki - Hätäkeskuslaitos

Page Load Speed

3.5 sec in total

First Response

361 ms

Resources Loaded

2.8 sec

Page Rendered

333 ms

112.fi screenshot

About Website

Click here to check amazing 112 content for Finland. Otherwise, check out these important facts you probably never knew about 112.fi

Hätäkeskuslaitos on sisäministeriön alainen valtakunnallinen, verkottuneen toimintamallin mukainen virasto. Hätäkeskuslaitoksen lakisääteisenä tehtävänä on hätätilanteita koskevien hätäpuheluiden vast...

Visit 112.fi

Key Findings

We analyzed 112.fi page load time and found that the first response time was 361 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

112.fi performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value1,930 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.125

83/100

15%

TTI (Time to Interactive)

Value15.2 s

7/100

10%

Network Requests Diagram

112.fi

361 ms

www.112.fi

892 ms

jquery-1.4.2.min.js

78 ms

compiled.aspx

640 ms

screen

534 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 94% of them (59 requests) were addressed to the original 112.fi, 3% (2 requests) were made to Eu1.snoobi.com and 2% (1 request) were made to Ajax.aspnetcdn.com. The less responsive or slowest element that took the longest time to load (892 ms) belongs to the original domain 112.fi.

Page Optimization Overview & Recommendations

Page size can be reduced by 459.1 kB (54%)

Content Size

847.6 kB

After Optimization

388.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of 112.fi main page is 847.6 kB. 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. Javascripts take 533.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 94.1 kB

  • Original 121.3 kB
  • After minification 100.9 kB
  • After compression 27.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. This page needs HTML code to be minified as it can gain 20.4 kB, which is 17% 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 94.1 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 9.2 kB

  • Original 192.4 kB
  • After minification 183.2 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. 112 images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 355.9 kB

  • Original 533.9 kB
  • After minification 521.3 kB
  • After compression 178.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 355.9 kB or 67% of the original size.

Requests Breakdown

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

Requests Now

61

After Optimization

35

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

112.fi

112.fi

361 ms

www.112.fi

www.112.fi

892 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

78 ms

compiled.aspx

compiled.aspx

640 ms

screen

screen

534 ms

css_colorbox.aspx

css_colorbox.aspx

331 ms

jquery.main.js

jquery.main.js

567 ms

WebResource.axd

WebResource.axd

117 ms

snoop.php

snoop.php

216 ms

bg-body.gif

bg-body.gif

166 ms

d2ec4304e1f02e41bf9a9933ed6dbc6bc146fc26.jpg

d2ec4304e1f02e41bf9a9933ed6dbc6bc146fc26.jpg

166 ms

2ae94ad62fcbeda6cb8d49e2071d0224f39aea83.jpg

2ae94ad62fcbeda6cb8d49e2071d0224f39aea83.jpg

737 ms

e4ee805c6c8f5d4e83f6732d64c225e0b8e7da97.jpg

e4ee805c6c8f5d4e83f6732d64c225e0b8e7da97.jpg

233 ms

bef2b9a4d471b309058de56a931d18cdf4579ed7.jpg

bef2b9a4d471b309058de56a931d18cdf4579ed7.jpg

166 ms

808c8bb504aa8c45afdbbb090aa47ac721f7435c.jpg

808c8bb504aa8c45afdbbb090aa47ac721f7435c.jpg

436 ms

0d6297af3990ab80d7599bf9c84fb5604eb8f045.jpg

0d6297af3990ab80d7599bf9c84fb5604eb8f045.jpg

238 ms

89d7fd03a708b607a8334a657f11fcdd0f5f8293.jpg

89d7fd03a708b607a8334a657f11fcdd0f5f8293.jpg

241 ms

arrow03.gif

arrow03.gif

246 ms

516357116cb81d4ec8a3e65989be42ce12b80e27.jpg

516357116cb81d4ec8a3e65989be42ce12b80e27.jpg

341 ms

icon-rss.png

icon-rss.png

344 ms

71f9f3e43db1e7baf0d2ff0120e4edd698aaf584.jpg

71f9f3e43db1e7baf0d2ff0120e4edd698aaf584.jpg

356 ms

icon-print.png

icon-print.png

361 ms

icon-feed.png

icon-feed.png

459 ms

f9b456ff6b6d1d9e7fb803083fa2eae101c4d262.jpg

f9b456ff6b6d1d9e7fb803083fa2eae101c4d262.jpg

461 ms

12c54f56c1c9cde5940ec615c3ec93e0681c709f.jpg

12c54f56c1c9cde5940ec615c3ec93e0681c709f.jpg

469 ms

d6fb0eaeb0eaa7b80b98b5441cbb3321759f4e00.jpg

d6fb0eaeb0eaa7b80b98b5441cbb3321759f4e00.jpg

474 ms

fa64505f3c91e18e7cbc7af56ecf522e11f3d4fc.jpg

fa64505f3c91e18e7cbc7af56ecf522e11f3d4fc.jpg

541 ms

7e3e562e44db08827e420aa18d28a1b5375c8bb8.jpg

7e3e562e44db08827e420aa18d28a1b5375c8bb8.jpg

569 ms

3678974dbd30e693819b4273bddf52f508cee552.jpg

3678974dbd30e693819b4273bddf52f508cee552.jpg

569 ms

07ccb939147907d13e779137a3c88963103b0458.jpg

07ccb939147907d13e779137a3c88963103b0458.jpg

577 ms

icon-info.png

icon-info.png

588 ms

icon-top.png

icon-top.png

648 ms

bg-page-t.png

bg-page-t.png

661 ms

bg-page-b.png

bg-page-b.png

660 ms

bg-page.gif

bg-page.gif

669 ms

bg-hbox.gif

bg-hbox.gif

685 ms

logo.png

logo.png

739 ms

sep01.gif

sep01.gif

768 ms

bg-hnav.gif

bg-hnav.gif

768 ms

bg-nav.png

bg-nav.png

779 ms

bg-drop-cl2.png

bg-drop-cl2.png

798 ms

bg-drop-cr2.png

bg-drop-cr2.png

824 ms

bg-drop-bl2.png

bg-drop-bl2.png

845 ms

bg-drop-b.png

bg-drop-b.png

876 ms

bg-drop-br.png

bg-drop-br.png

876 ms

snoop2.php

snoop2.php

120 ms

bg-drop-tl2.png

bg-drop-tl2.png

746 ms

bg-drop-t.png

bg-drop-t.png

771 ms

bg-drop-tr.png

bg-drop-tr.png

793 ms

arrow01.png

arrow01.png

743 ms

arrow02.png

arrow02.png

772 ms

arrow03.gif

arrow03.gif

766 ms

bg-footer-t.png

bg-footer-t.png

775 ms

bg-footer-b.png

bg-footer-b.png

708 ms

bg-footer.gif

bg-footer.gif

727 ms

overlay.png

overlay.png

726 ms

controls.png

controls.png

756 ms

border.png

border.png

683 ms

loading_background.png

loading_background.png

670 ms

loading.gif

loading.gif

702 ms

bg-switch.png

bg-switch.png

712 ms

print

print

113 ms

addthis_widget.js

addthis_widget.js

12 ms

Accessibility Review

112.fi accessibility score

93

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

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

112.fi SEO score

90

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

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

112.fi

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