Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

emta.ee

Eraklient | Maksu- ja Tolliamet

Page Load Speed

4.2 sec in total

First Response

355 ms

Resources Loaded

3.5 sec

Page Rendered

319 ms

emta.ee screenshot

About Website

Welcome to emta.ee homepage info - get ready to check Emta best content for Estonia right away, or after learning these important things about emta.ee

Visit emta.ee

Key Findings

We analyzed Emta.ee page load time and found that the first response time was 355 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

emta.ee performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.18

67/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

emta.ee

355 ms

emta.ee

629 ms

js

57 ms

css_o6ZhTo0WCvI5L2knf5ZmL1Qc_fhphJqTIDYCZHY5vrU.css

246 ms

css_hjjZCA1xJxAKQzAHJ8y5iRQUvKRNN5BIVb1U27deylY.css

589 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 74% of them (37 requests) were addressed to the original Emta.ee, 14% (7 requests) were made to I.ytimg.com and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Buerokratt.emta.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 829.4 kB (16%)

Content Size

5.1 MB

After Optimization

4.3 MB

In fact, the total size of Emta.ee main page is 5.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. 50% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 160.6 kB

  • Original 182.7 kB
  • After minification 158.1 kB
  • After compression 22.1 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 24.6 kB, which is 13% 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 160.6 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 4 B

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

JavaScript Optimization

-48%

Potential reduce by 668.7 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 738.9 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 668.7 kB or 48% of the original size.

CSS Optimization

-0%

Potential reduce by 99 B

  • Original 89.8 kB
  • After minification 89.8 kB
  • After compression 89.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. Emta.ee has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (28%)

Requests Now

43

After Optimization

31

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

Accessibility Review

emta.ee accessibility score

91

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

Best Practices

emta.ee 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

emta.ee SEO score

73

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

    ET

  • Language Claimed

    ET

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Emta.ee can be misinterpreted by Google and other search engines. Our service has detected that Estonian is used on the page, and it matches the claimed language. Our system also found out that Emta.ee 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 Emta. 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: