Tools & Wizards About Us
edde.ru screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

edde.ru

EDISON — создание сайтов в Череповце. Интернет-магазины, SEO, продвижение, лендинги

Page Load Speed

5.3 sec in total

First Response

640 ms

Resources Loaded

3.8 sec

Page Rendered

865 ms

edde.ru screenshot

About Website

Visit edde.ru now to see the best up-to-date Edde content and also check out these interesting facts you probably never knew about edde.ru

Дизайн-студия EDISON - создание сайтов, интернет-магазинов, лендингов в Череповце, SEO, продвижение сайтов в интернете

Visit edde.ru

Key Findings

We analyzed Edde.ru page load time and found that the first response time was 640 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

edde.ru performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value1,950 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.296

40/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

edde.ru

640 ms

style.css

256 ms

component.css

258 ms

modernizr.custom.js

261 ms

jquery-1.10.1.min.js

383 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 88% of them (105 requests) were addressed to the original Edde.ru, 3% (4 requests) were made to 64424.selcdn.ru and 2% (2 requests) were made to Call.beget.ru. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Edde.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 491.8 kB (18%)

Content Size

2.8 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Edde.ru main page is 2.8 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. 65% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 205.3 kB

  • Original 293.6 kB
  • After minification 275.9 kB
  • After compression 88.3 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 205.3 kB or 70% of the original size.

Image Optimization

-1%

Potential reduce by 18.5 kB

  • Original 2.1 MB
  • After minification 2.0 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. Edde images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 242.7 kB

  • Original 353.9 kB
  • After minification 316.7 kB
  • After compression 111.2 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 242.7 kB or 69% of the original size.

CSS Optimization

-27%

Potential reduce by 25.3 kB

  • Original 92.7 kB
  • After minification 86.2 kB
  • After compression 67.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. Edde.ru needs all CSS files to be minified and compressed as it can save up to 25.3 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (23%)

Requests Now

110

After Optimization

85

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

edde.ru

edde.ru

640 ms

style.css

style.css

256 ms

component.css

component.css

258 ms

modernizr.custom.js

modernizr.custom.js

261 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

383 ms

jquery.mousewheel-3.0.6.pack.js

jquery.mousewheel-3.0.6.pack.js

259 ms

jquery.fancybox.js

jquery.fancybox.js

261 ms

jquery.fancybox.css

jquery.fancybox.css

379 ms

style-slide.css

style-slide.css

377 ms

custom.js

custom.js

379 ms

jquery.fancybox.css

jquery.fancybox.css

379 ms

jquery.js

jquery.js

555 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

507 ms

jquery.fancybox-1.2.1.pack.js

jquery.fancybox-1.2.1.pack.js

507 ms

callme.js

callme.js

506 ms

style.css

style.css

962 ms

057225edcf37b99cdcb1e84b1da65d65.js

057225edcf37b99cdcb1e84b1da65d65.js

833 ms

toucheffects.js

toucheffects.js

504 ms

239 ms

urchin.js

urchin.js

15 ms

521 ms

ubuntu.css

ubuntu.css

31 ms

config.js

config.js

127 ms

style.css

style.css

127 ms

f.php

f.php

148 ms

logo3.png

logo3.png

182 ms

3_1_FFFFFFFF_EFEFEFFF_0_pageviews

3_1_FFFFFFFF_EFEFEFFF_0_pageviews

468 ms

location.png

location.png

136 ms

v3.jpg

v3.jpg

643 ms

logos.png

logos.png

132 ms

fact.png

fact.png

133 ms

c_09.jpg

c_09.jpg

152 ms

a_up.png

a_up.png

464 ms

case_logo_09.png

case_logo_09.png

466 ms

case_09.png

case_09.png

473 ms

c_08.jpg

c_08.jpg

467 ms

case_logo_08.png

case_logo_08.png

467 ms

case_08.png

case_08.png

480 ms

c_10.jpg

c_10.jpg

470 ms

case_logo_10.png

case_logo_10.png

472 ms

case_10.png

case_10.png

509 ms

c_06.jpg

c_06.jpg

507 ms

case_logo_06.png

case_logo_06.png

504 ms

case_06.png

case_06.png

507 ms

c_07.jpg

c_07.jpg

598 ms

case_logo_07.png

case_logo_07.png

629 ms

case_07.png

case_07.png

756 ms

c_05.jpg

c_05.jpg

631 ms

case_logo_05.png

case_logo_05.png

634 ms

case_05.png

case_05.png

721 ms

c_04.jpg

c_04.jpg

753 ms

case_logo_04.png

case_logo_04.png

755 ms

case_04.png

case_04.png

758 ms

c_03.jpg

c_03.jpg

759 ms

case_logo_03.png

case_logo_03.png

845 ms

case_03.png

case_03.png

1015 ms

c_02.jpg

c_02.jpg

877 ms

case_logo_02.png

case_logo_02.png

879 ms

case_02.png

case_02.png

1025 ms

c_01.jpg

c_01.jpg

888 ms

case_logo_01.png

case_logo_01.png

996 ms

case_01.png

case_01.png

1015 ms

400.woff

400.woff

407 ms

500.woff

500.woff

671 ms

300.woff

300.woff

831 ms

700.woff

700.woff

812 ms

PFBeauSansPro-Bold.otf

PFBeauSansPro-Bold.otf

1172 ms

PFBeauSansPro-Light.otf

PFBeauSansPro-Light.otf

1043 ms

site_bg.jpg

site_bg.jpg

1008 ms

mini_dedal.png

mini_dedal.png

1129 ms

mini_nissan.png

mini_nissan.png

1002 ms

__utm.gif

__utm.gif

290 ms

watch.js

watch.js

286 ms

mini_tepl.png

mini_tepl.png

699 ms

mini_gw.png

mini_gw.png

803 ms

mini_teko.png

mini_teko.png

938 ms

mini_optik.png

mini_optik.png

820 ms

mini_orion.png

mini_orion.png

842 ms

mini_ras.png

mini_ras.png

923 ms

mini_ts.png

mini_ts.png

926 ms

mini_exp.png

mini_exp.png

938 ms

mini_par.png

mini_par.png

919 ms

mini_ford.png

mini_ford.png

921 ms

mini_med.png

mini_med.png

1013 ms

mini_trans.png

mini_trans.png

1022 ms

mini_01.png

mini_01.png

930 ms

mini_sep2.png

mini_sep2.png

914 ms

mini_motobloki.png

mini_motobloki.png

919 ms

mini_anga.png

mini_anga.png

919 ms

mini_spartpit.png

mini_spartpit.png

1007 ms

mini_sew.png

mini_sew.png

933 ms

mini_ag.png

mini_ag.png

898 ms

mini_laundry.png

mini_laundry.png

914 ms

mini_pizza.png

mini_pizza.png

918 ms

mini_techno35.png

mini_techno35.png

919 ms

mini_profilcentr.png

mini_profilcentr.png

1007 ms

mini_premium.png

mini_premium.png

931 ms

mini_02.png

mini_02.png

899 ms

mini_mishka.png

mini_mishka.png

912 ms

mini_sk.png

mini_sk.png

908 ms

mini_ton.png

mini_ton.png

804 ms

mini_vent.png

mini_vent.png

876 ms

mini_vasha.png

mini_vasha.png

887 ms

mini_inv.png

mini_inv.png

876 ms

mini_yoga.png

mini_yoga.png

787 ms

mini_1001.png

mini_1001.png

778 ms

mini_proenergo.png

mini_proenergo.png

772 ms

mini_sep.png

mini_sep.png

839 ms

mini_haus.png

mini_haus.png

768 ms

mini_03.png

mini_03.png

757 ms

01-flower.png

01-flower.png

764 ms

01-sep.png

01-sep.png

746 ms

01-piz.png

01-piz.png

711 ms

counter2

counter2

160 ms

01-ton.png

01-ton.png

758 ms

logo_footer.png

logo_footer.png

756 ms

ok1.png

ok1.png

756 ms

hr_line2.png

hr_line2.png

765 ms

hr_vert.png

hr_vert.png

760 ms

Accessibility Review

edde.ru accessibility score

63

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

button, link, and menuitem elements do not have accessible names.

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

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

edde.ru best practices score

58

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

edde.ru SEO score

69

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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edde.ru 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 Edde.ru main page’s claimed encoding is windows-1251. 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

edde.ru

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