Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

nh.ee

Delfi

Page Load Speed

4.4 sec in total

First Response

304 ms

Resources Loaded

2.5 sec

Page Rendered

1.6 sec

nh.ee screenshot

About Website

Click here to check amazing Nh content for Russia. Otherwise, check out these important facts you probably never knew about nh.ee

Eesti suurim uudisteportaal, mis koondab endas Eesti ja välisuudised, krimiuudised, arvamuslood, ilmainfo ning palju muud

Visit nh.ee

Key Findings

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

Performance Metrics

nh.ee performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value22.9 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value4,780 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value28.6 s

0/100

10%

Network Requests Diagram

www.delfi.ee

304 ms

inter.css

212 ms

roboto.css

214 ms

delfi-root-variables-css.css

91 ms

main-root-styles.css

100 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Nh.ee, 22% (15 requests) were made to G.delfi.ee and 16% (11 requests) were made to Ee-production-portal-root.s3.delfi.ee. The less responsive or slowest element that took the longest time to load (745 ms) relates to the external source S1.adform.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 419.5 kB (29%)

Content Size

1.4 MB

After Optimization

1.0 MB

In fact, the total size of Nh.ee main page is 1.4 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. 35% of websites need less resources to load. Javascripts take 886.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 416.3 kB

  • Original 524.0 kB
  • After minification 518.0 kB
  • After compression 107.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. 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 416.3 kB or 79% of the original size.

JavaScript Optimization

-0%

Potential reduce by 3.1 kB

  • Original 886.8 kB
  • After minification 886.8 kB
  • After compression 883.7 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

-1%

Potential reduce by 182 B

  • Original 34.5 kB
  • After minification 34.5 kB
  • After compression 34.3 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. Nh.ee has all CSS files already compressed.

Requests Breakdown

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

Requests Now

66

After Optimization

46

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

Accessibility Review

nh.ee accessibility score

69

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

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

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

nh.ee SEO score

82

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 Nh.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 Nh.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 Nh. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: