Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 55% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

hortes.ee

Aianduskeskus Hortes: taimed, töövahendid ja sisustus aeda ja koju

Page Load Speed

11.7 sec in total

First Response

344 ms

Resources Loaded

6.1 sec

Page Rendered

5.2 sec

hortes.ee screenshot

About Website

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

Aianduskeskus Hortes on iga aiaomaniku paradiis. Sind ootavad õue- ja toataimed, kõik kaunis kodu sisustamiseks ja parim sinu lemmikule.

Visit hortes.ee

Key Findings

We analyzed Hortes.ee page load time and found that the first response time was 344 ms and then it took 11.3 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

hortes.ee performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value4,100 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.073

95/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

hortes.ee

344 ms

hortes.ee

2048 ms

analytics.js

36 ms

gtm.js

88 ms

uc.js

50 ms

Our browser made a total of 156 requests to load all elements on the main page. We found that 81% of them (127 requests) were addressed to the original Hortes.ee, 5% (8 requests) were made to Fonts.gstatic.com and 4% (7 requests) were made to Js.klevu.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Hortes.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (6%)

Content Size

40.4 MB

After Optimization

38.1 MB

In fact, the total size of Hortes.ee main page is 40.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. Only a small number of websites need less resources to load. Images take 38.9 MB which makes up the majority of the site volume.

HTML Optimization

-94%

Potential reduce by 603.9 kB

  • Original 640.9 kB
  • After minification 502.0 kB
  • After compression 37.0 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 138.9 kB, which is 22% 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 603.9 kB or 94% of the original size.

Image Optimization

-4%

Potential reduce by 1.7 MB

  • Original 38.9 MB
  • After minification 37.2 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. Hortes images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 42.9 kB

  • Original 781.2 kB
  • After minification 781.2 kB
  • After compression 738.4 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 639 B

  • Original 127.5 kB
  • After minification 127.5 kB
  • After compression 126.9 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. Hortes.ee has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 48 (33%)

Requests Now

145

After Optimization

97

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

Accessibility Review

hortes.ee accessibility score

83

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-hidden="true"] elements contain focusable descendents

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

[id] attributes on active, focusable elements are not unique

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

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

Links do not have a discernible name

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

hortes.ee best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

hortes.ee SEO score

86

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

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