Report Summary

  • 16

    Performance

    Renders faster than
    35% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 90

    SEO

    Google-friendlier than
    73% of websites

epl.ee

Eesti Päevaleht

Page Load Speed

14.5 sec in total

First Response

492 ms

Resources Loaded

11.9 sec

Page Rendered

2.2 sec

epl.ee screenshot

About Website

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

Eesti Päevaleht ilmub esmaspäevast neljapäevani ning reedel ilmub mahukam nädalalõpuleht LP. Lehe toimetusse kuuluvad tunnustatud ajakirjanikud, kes teevad Eesti parimat ajakirjandust. Iga eestlane vä...

Visit epl.ee

Key Findings

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

Performance Metrics

epl.ee performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value15.9 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value7,960 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value24.7 s

0/100

10%

Network Requests Diagram

epl.delfi.ee

492 ms

b64_global.css

736 ms

b64_fp12.css

855 ms

387 ms

392 ms

Our browser made a total of 554 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Epl.ee, 8% (45 requests) were made to Delfiadee.hit.gemius.pl and 5% (27 requests) were made to G2.nh.ee. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Cdn.goroost.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (27%)

Content Size

6.7 MB

After Optimization

4.9 MB

In fact, the total size of Epl.ee main page is 6.7 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 245.2 kB

  • Original 327.6 kB
  • After minification 322.3 kB
  • After compression 82.4 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 245.2 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 69.1 kB

  • Original 4.2 MB
  • After minification 4.1 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. Epl images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 984.9 kB

  • Original 1.4 MB
  • After minification 1.3 MB
  • After compression 409.5 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 984.9 kB or 71% of the original size.

CSS Optimization

-59%

Potential reduce by 502.0 kB

  • Original 849.7 kB
  • After minification 841.8 kB
  • After compression 347.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. Epl.ee needs all CSS files to be minified and compressed as it can save up to 502.0 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 266 (50%)

Requests Now

532

After Optimization

266

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

Accessibility Review

epl.ee accessibility score

63

Accessibility Issues

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

Buttons do not have an accessible name

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

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

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

epl.ee best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

epl.ee SEO score

90

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ET

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epl.ee can be misinterpreted by Google and other search engines. Our service has detected that Estonian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Epl.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 data is detected on the main page of Epl. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: