Tools & Wizards About Us

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

erle.ee

sussikott, kotid, kotid lastele, sussikotid nimega, logoga kotid, masintikand

Page Load Speed

6.6 sec in total

First Response

392 ms

Resources Loaded

6 sec

Page Rendered

146 ms

About Website

Visit erle.ee now to see the best up-to-date Erle content and also check out these interesting facts you probably never knew about erle.ee

kotid, sussikott nimetikandiga, jalatsikott, masintikandiga tooted, lasteaia kott, nimeline kott, masintikkimine, pidžaamakott, kangast kott eco kott, öko kott, taaskasutatav kott

Visit erle.ee

Key Findings

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

Performance Metrics

erle.ee performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.311

37/100

15%

TTI (Time to Interactive)

Value9.7 s

29/100

10%

Network Requests Diagram

erle.ee

392 ms

erle.ee

3978 ms

css

32 ms

css

47 ms

bootstrap.css

698 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Erle.ee, 80% (39 requests) were made to Lasteriidepuu.ee and 12% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Erle.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 307.5 kB (53%)

Content Size

577.6 kB

After Optimization

270.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Erle.ee main page is 577.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. 40% of websites need less resources to load. HTML takes 241.0 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 222.3 kB

  • Original 241.0 kB
  • After minification 214.8 kB
  • After compression 18.7 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 26.2 kB, which is 11% 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 222.3 kB or 92% of the original size.

Image Optimization

-40%

Potential reduce by 32.8 kB

  • Original 82.4 kB
  • After minification 49.5 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. Obviously, Erle needs image optimization as it can save up to 32.8 kB or 40% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 16.1 kB

  • Original 121.2 kB
  • After minification 121.2 kB
  • After compression 105.1 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 16.1 kB or 13% of the original size.

CSS Optimization

-27%

Potential reduce by 36.2 kB

  • Original 133.0 kB
  • After minification 133.0 kB
  • After compression 96.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. Erle.ee needs all CSS files to be minified and compressed as it can save up to 36.2 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (77%)

Requests Now

39

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

erle.ee accessibility score

87

Accessibility Issues

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.

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

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

Page has valid source maps

SEO Factors

erle.ee SEO score

79

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 Erle.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 Erle.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 Erle. 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: