Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

devorex.ee

Suusareisid | Stiilne Puhkus - suusapuhkus, jahirent, kalastusreisid, rannapuhkus

Page Load Speed

5.6 sec in total

First Response

949 ms

Resources Loaded

4.4 sec

Page Rendered

237 ms

devorex.ee screenshot

About Website

Welcome to devorex.ee homepage info - get ready to check Devorex best content right away, or after learning these important things about devorex.ee

Suusareisid Alpidesse, Andorrasse ja Skandinaaviasse. Suurim valik Eestis – rohkem kui 30 suusakeskust.

Visit devorex.ee

Key Findings

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

devorex.ee performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

devorex.ee

949 ms

style.css

498 ms

jquery.min.js

29 ms

modernizr-2.5.2.js

799 ms

jquery.colorbox-min.js

133 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 95% of them (55 requests) were addressed to the original Devorex.ee, 3% (2 requests) were made to Stats.g.doubleclick.net and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Devorex.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 159.9 kB (27%)

Content Size

597.2 kB

After Optimization

437.2 kB

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

HTML Optimization

-78%

Potential reduce by 18.6 kB

  • Original 23.8 kB
  • After minification 20.6 kB
  • After compression 5.2 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 3.2 kB, which is 14% 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 18.6 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 17.7 kB

  • Original 373.6 kB
  • After minification 355.9 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. Devorex images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 66.9 kB

  • Original 131.3 kB
  • After minification 90.0 kB
  • After compression 64.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 66.9 kB or 51% of the original size.

CSS Optimization

-83%

Potential reduce by 56.8 kB

  • Original 68.6 kB
  • After minification 52.9 kB
  • After compression 11.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. Devorex.ee needs all CSS files to be minified and compressed as it can save up to 56.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (16%)

Requests Now

57

After Optimization

48

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

Accessibility Review

devorex.ee accessibility score

73

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

[role] values are not valid

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

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

devorex.ee best practices score

75

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

Missing source maps for large first-party JavaScript

SEO Factors

devorex.ee SEO score

88

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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