Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

diabetes.ee

Avaleht - Eesti Diabeediliit

Page Load Speed

2 sec in total

First Response

387 ms

Resources Loaded

1.4 sec

Page Rendered

153 ms

diabetes.ee screenshot

About Website

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

Visit diabetes.ee

Key Findings

We analyzed Diabetes.ee page load time and found that the first response time was 387 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

diabetes.ee performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.512

15/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

diabetes.ee

387 ms

www.diabetes.ee

580 ms

stiilid.css

121 ms

toptaust.jpg

123 ms

pilt.php

342 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that all of those requests were addressed to Diabetes.ee and no external sources were called. The less responsive or slowest element that took the longest time to load (580 ms) belongs to the original domain Diabetes.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 6.9 kB (35%)

Content Size

19.5 kB

After Optimization

12.6 kB

In fact, the total size of Diabetes.ee main page is 19.5 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. Only 5% of websites need less resources to load. Images take 11.8 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 3.7 kB

  • Original 5.6 kB
  • After minification 5.0 kB
  • After compression 1.9 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 3.7 kB or 66% of the original size.

Image Optimization

-14%

Potential reduce by 1.6 kB

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

CSS Optimization

-73%

Potential reduce by 1.6 kB

  • Original 2.1 kB
  • After minification 1.7 kB
  • After compression 580 B

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. Diabetes.ee needs all CSS files to be minified and compressed as it can save up to 1.6 kB or 73% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

7

After Optimization

7

The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Diabetes. According to our analytics all requests are already optimized.

Accessibility Review

diabetes.ee accessibility score

80

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

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.

Best Practices

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

SEO Factors

diabetes.ee SEO score

84

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Diabetes.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 Diabetes.ee main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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