Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

edinorog.org

Купить настольные игры в магазине «bgames.ru»!

Page Load Speed

10.7 sec in total

First Response

572 ms

Resources Loaded

9.6 sec

Page Rendered

453 ms

About Website

Click here to check amazing Edinorog content for Russia. Otherwise, check out these important facts you probably never knew about edinorog.org

Купить настольные игры в интернет-магазине bgames.ru. Лучшие настольные игры для детей и взрослых. Бесплатная доставка от 3000 руб

Visit edinorog.org

Key Findings

We analyzed Edinorog.org page load time and found that the first response time was 572 ms and then it took 10.1 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

edinorog.org performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value37.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value48.3 s

0/100

25%

SI (Speed Index)

Value58.2 s

0/100

10%

TBT (Total Blocking Time)

Value8,140 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.155

74/100

15%

TTI (Time to Interactive)

Value60.9 s

0/100

10%

Network Requests Diagram

edinorog.org

572 ms

get_js

589 ms

insales_counter.js

139 ms

jquery.fancybox.css

283 ms

default.css

287 ms

Our browser made a total of 155 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Edinorog.org, 53% (82 requests) were made to Static-eu.insales.ru and 21% (32 requests) were made to Assets3.insales.ru. The less responsive or slowest element that took the longest time to load (5.5 sec) relates to the external source Static-eu.insales.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 642.4 kB (13%)

Content Size

4.9 MB

After Optimization

4.3 MB

In fact, the total size of Edinorog.org main page is 4.9 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. Images take 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 222.2 kB

  • Original 261.2 kB
  • After minification 191.7 kB
  • After compression 39.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 69.5 kB, which is 27% 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 222.2 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 166.5 kB

  • Original 4.2 MB
  • After minification 4.1 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. Edinorog images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 155.4 kB

  • Original 299.3 kB
  • After minification 286.0 kB
  • After compression 143.9 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 155.4 kB or 52% of the original size.

CSS Optimization

-83%

Potential reduce by 98.2 kB

  • Original 118.4 kB
  • After minification 92.8 kB
  • After compression 20.2 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. Edinorog.org needs all CSS files to be minified and compressed as it can save up to 98.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (26%)

Requests Now

145

After Optimization

108

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

Accessibility Review

edinorog.org accessibility score

88

Accessibility Issues

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.

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

<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

Best Practices

edinorog.org 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

edinorog.org SEO score

84

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

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edinorog.org can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Edinorog.org 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 Edinorog. 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: