Tools & Wizards About Us
toode.ee screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

toode.ee

Katused | Toode AS - katused, vihmaveesüsteemid, katusetarvikud

Page Load Speed

4.9 sec in total

First Response

350 ms

Resources Loaded

4.4 sec

Page Rendered

177 ms

toode.ee screenshot

About Website

Click here to check amazing Toode content for Estonia. Otherwise, check out these important facts you probably never knew about toode.ee

Katus Toode AS pakub katuseid ja vihmaveesüsteeme. Aitame ehitada uue kvaliteet katuse, kasutades kaasaegsemat tehnikat. Ettevõtte aastast 1991

Visit toode.ee

Key Findings

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

Performance Metrics

toode.ee performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value5,180 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.699

7/100

15%

TTI (Time to Interactive)

Value19.2 s

2/100

10%

Network Requests Diagram

toode.ee

350 ms

www.toode.ee

825 ms

2bac0.default.include.f07146.css

227 ms

2bac0.default.include.8c2c9a.js

664 ms

style.min.css

344 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 78% of them (54 requests) were addressed to the original Toode.ee, 4% (3 requests) were made to Cdnjs.cloudflare.com and 3% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (983 ms) belongs to the original domain Toode.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 203.9 kB (14%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 97.6 kB

  • Original 119.1 kB
  • After minification 104.3 kB
  • After compression 21.5 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 14.8 kB, which is 12% 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 97.6 kB or 82% of the original size.

Image Optimization

-19%

Potential reduce by 99.4 kB

  • Original 519.8 kB
  • After minification 420.4 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, Toode needs image optimization as it can save up to 99.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 5.5 kB

  • Original 730.1 kB
  • After minification 729.9 kB
  • After compression 724.6 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

-2%

Potential reduce by 1.4 kB

  • Original 86.7 kB
  • After minification 86.7 kB
  • After compression 85.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. Toode.ee has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (65%)

Requests Now

63

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

toode.ee

toode.ee

350 ms

www.toode.ee

www.toode.ee

825 ms

2bac0.default.include.f07146.css

2bac0.default.include.f07146.css

227 ms

2bac0.default.include.8c2c9a.js

2bac0.default.include.8c2c9a.js

664 ms

style.min.css

style.min.css

344 ms

frontend.css

frontend.css

341 ms

all.min.css

all.min.css

41 ms

styles.css

styles.css

341 ms

style.min.css

style.min.css

366 ms

wppopups-base.css

wppopups-base.css

366 ms

cms-navigation-base.css

cms-navigation-base.css

455 ms

cms-navigation.css

cms-navigation.css

454 ms

gdpr-main.css

gdpr-main.css

458 ms

jquery.min.js

jquery.min.js

488 ms

jquery-migrate.min.js

jquery-migrate.min.js

485 ms

wpgmza_data.js

wpgmza_data.js

568 ms

script.min.js

script.min.js

568 ms

font-awesome.min.css

font-awesome.min.css

43 ms

css

css

47 ms

api.js

api.js

47 ms

2bac0.default.include-body.8a5cef.js

2bac0.default.include-body.8a5cef.js

571 ms

cherry-api.min.js

cherry-api.min.js

602 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

605 ms

device.min.js

device.min.js

771 ms

parallax.min.js

parallax.min.js

771 ms

init.min.js

init.min.js

771 ms

swiper.jquery.min.js

swiper.jquery.min.js

771 ms

custom.js

custom.js

771 ms

js

js

79 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

790 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

814 ms

wp-polyfill.min.js

wp-polyfill.min.js

815 ms

hooks.min.js

hooks.min.js

813 ms

wppopups.js

wppopups.js

868 ms

frontend.min.js

frontend.min.js

983 ms

index.js

index.js

906 ms

index.js

index.js

932 ms

api.js

api.js

67 ms

index.js

index.js

931 ms

main.js

main.js

932 ms

gtm.js

gtm.js

120 ms

recaptcha__en.js

recaptcha__en.js

66 ms

logo.png

logo.png

230 ms

timthumb.php

timthumb.php

394 ms

timthumb.php

timthumb.php

396 ms

timthumb.php

timthumb.php

395 ms

timthumb.php

timthumb.php

397 ms

gdpr-logo.png

gdpr-logo.png

397 ms

search_button.png

search_button.png

386 ms

font

font

79 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

30 ms

js

js

73 ms

fbevents.js

fbevents.js

63 ms

askquote_ee.png

askquote_ee.png

168 ms

request_ee.png

request_ee.png

170 ms

solar_btn.png

solar_btn.png

169 ms

452170632718750

452170632718750

194 ms

prev.svg

prev.svg

138 ms

next.svg

next.svg

118 ms

play.svg

play.svg

115 ms

pause.svg

pause.svg

119 ms

timthumb.php

timthumb.php

252 ms

timthumb.php

timthumb.php

254 ms

timthumb.php

timthumb.php

173 ms

timthumb.php

timthumb.php

345 ms

timthumb.php

timthumb.php

344 ms

fa-solid-900.woff

fa-solid-900.woff

55 ms

fa-regular-400.woff

fa-regular-400.woff

77 ms

grab.svg

grab.svg

117 ms

Accessibility Review

toode.ee accessibility score

86

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

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

toode.ee SEO score

90

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

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

toode.ee

Open Graph description is not detected on the main page of Toode. 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: