Tools & Wizards About Us
eglo.pro screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

eglo.pro

Купить светильники EGLO оптом и в розницу у официального партнера ЭГЛО в России. Более 5000 наименований в интернет-магазине EGLO.PRO

Page Load Speed

2.1 sec in total

First Response

402 ms

Resources Loaded

1.6 sec

Page Rendered

78 ms

eglo.pro screenshot

About Website

Visit eglo.pro now to see the best up-to-date EGLO content for Russia and also check out these interesting facts you probably never knew about eglo.pro

Магазин EGLO.PRO - официальный дистрибьютор австрийской марки ЭГЛО в России. На сайте Вы можете купить светильники с бесплатной доставкой по России, скачать online каталоги.

Visit eglo.pro

Key Findings

We analyzed Eglo.pro page load time and found that the first response time was 402 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

eglo.pro performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

eglo.pro

402 ms

bundle.eecf1ce51a756bdc385b.bundle.js

412 ms

external.bundle.js

268 ms

internal.bundle.js

283 ms

ParkingPage.f3a42e12de40e2d45a4b.bundle.js

520 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 11.5 kB (52%)

Content Size

22.1 kB

After Optimization

10.7 kB

  • HTML
  • CSS

In fact, the total size of Eglo.pro main page is 22.1 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. 20% of websites need less resources to load. HTML takes 15.0 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 9.8 kB

  • Original 15.0 kB
  • After minification 14.4 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. 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 9.8 kB or 65% of the original size.

CSS Optimization

-24%

Potential reduce by 1.7 kB

  • Original 7.1 kB
  • After minification 7.1 kB
  • After compression 5.4 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. Eglo.pro needs all CSS files to be minified and compressed as it can save up to 1.7 kB or 24% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

eglo.pro

eglo.pro

402 ms

bundle.eecf1ce51a756bdc385b.bundle.js

bundle.eecf1ce51a756bdc385b.bundle.js

412 ms

external.bundle.js

external.bundle.js

268 ms

internal.bundle.js

internal.bundle.js

283 ms

ParkingPage.f3a42e12de40e2d45a4b.bundle.js

ParkingPage.f3a42e12de40e2d45a4b.bundle.js

520 ms

ParkingPage.f3a42e12de40e2d45a4b.css

ParkingPage.f3a42e12de40e2d45a4b.css

260 ms

NotoSans-Bold.ttf

NotoSans-Bold.ttf

654 ms

NotoSans-Regular.ttf

NotoSans-Regular.ttf

777 ms

Accessibility Review

eglo.pro accessibility score

86

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.

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

eglo.pro best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

eglo.pro SEO score

92

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

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 Eglo.pro 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 Eglo.pro 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

eglo.pro

Open Graph data is detected on the main page of EGLO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: