Tools & Wizards About Us
500w.ru screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

500w.ru

Page Load Speed

4.6 sec in total

First Response

942 ms

Resources Loaded

3.4 sec

Page Rendered

319 ms

500w.ru screenshot

About Website

Welcome to 500w.ru homepage info - get ready to check 500 W best content for Russia right away, or after learning these important things about 500w.ru

500W.RU Светодиодные прожекторы, светодиодные лампы, уличные светодиодные светильники, офисные светодиодные светильники, альтернативные источники света

Visit 500w.ru

Key Findings

We analyzed 500w.ru page load time and found that the first response time was 942 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

500w.ru performance score

0

Network Requests Diagram

500w.ru

942 ms

style.css

377 ms

jquery-1.9.1.min.js

6 ms

main.js

254 ms

lightbox.js

401 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 80% of them (63 requests) were addressed to the original 500w.ru, 9% (7 requests) were made to Static.olark.com and 5% (4 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain 500w.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 226.9 kB (37%)

Content Size

619.7 kB

After Optimization

392.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 500w.ru main page is 619.7 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. 35% of websites need less resources to load. Images take 385.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 36.1 kB

  • Original 46.7 kB
  • After minification 44.9 kB
  • After compression 10.6 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 36.1 kB or 77% of the original size.

Image Optimization

-12%

Potential reduce by 47.5 kB

  • Original 385.8 kB
  • After minification 338.3 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, 500 W needs image optimization as it can save up to 47.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-76%

Potential reduce by 118.1 kB

  • Original 156.2 kB
  • After minification 129.8 kB
  • After compression 38.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 118.1 kB or 76% of the original size.

CSS Optimization

-82%

Potential reduce by 25.3 kB

  • Original 31.0 kB
  • After minification 28.5 kB
  • After compression 5.6 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. 500w.ru needs all CSS files to be minified and compressed as it can save up to 25.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (29%)

Requests Now

66

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

500w.ru

500w.ru

942 ms

style.css

style.css

377 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

6 ms

main.js

main.js

254 ms

lightbox.js

lightbox.js

401 ms

jquery.carouFredSel-5.6.2.js

jquery.carouFredSel-5.6.2.js

544 ms

header.png

header.png

392 ms

logo.png

logo.png

267 ms

ico1.png

ico1.png

129 ms

btn1.png

btn1.png

377 ms

menu.png

menu.png

138 ms

search.png

search.png

254 ms

shadows.png

shadows.png

543 ms

board.png

board.png

274 ms

banner.jpg

banner.jpg

629 ms

on-off.png

on-off.png

393 ms

sliderbg.png

sliderbg.png

410 ms

sliderbgins.png

sliderbgins.png

503 ms

banner_01.jpg

banner_01.jpg

520 ms

banner_02.jpg

banner_02.jpg

524 ms

banner_03.jpg

banner_03.jpg

817 ms

arrs.png

arrs.png

628 ms

contbg.png

contbg.png

650 ms

dots1.png

dots1.png

659 ms

1716_1.jpg

1716_1.jpg

690 ms

1715_1.jpg

1715_1.jpg

765 ms

1714_1.jpg

1714_1.jpg

770 ms

1713_1.jpg

1713_1.jpg

786 ms

1712_1.jpg

1712_1.jpg

792 ms

1711_1.jpg

1711_1.jpg

830 ms

1710_1.jpg

1710_1.jpg

895 ms

1703_06981.jpg

1703_06981.jpg

899 ms

1700_1.jpg

1700_1.jpg

919 ms

1696_1.jpg

1696_1.jpg

927 ms

1695_08475.jpg

1695_08475.jpg

961 ms

1681_61728.jpg

1681_61728.jpg

971 ms

1678_70552.jpg

1678_70552.jpg

1024 ms

1677_71250.jpg

1677_71250.jpg

1030 ms

1673_06589.jpg

1673_06589.jpg

1050 ms

1672_07178.jpg

1672_07178.jpg

1063 ms

1671_07728.jpg

1671_07728.jpg

1099 ms

hit

hit

259 ms

1670_05054.jpg

1670_05054.jpg

1072 ms

watch.js

watch.js

226 ms

loader0.js

loader0.js

57 ms

5411-784-10-7736.js

5411-784-10-7736.js

137 ms

MYRIADPRO-BOLDCOND.woff

MYRIADPRO-BOLDCOND.woff

1167 ms

MYRIADPRO-BOLD.woff

MYRIADPRO-BOLD.woff

1168 ms

MYRIADPRO-COND.woff

MYRIADPRO-COND.woff

1075 ms

c

c

360 ms

MYRIADPRO-REGULAR.woff

MYRIADPRO-REGULAR.woff

1072 ms

1667_25187.jpg

1667_25187.jpg

976 ms

watch.js

watch.js

579 ms

1524_03505.jpg

1524_03505.jpg

883 ms

1490_36318.jpg

1490_36318.jpg

996 ms

1400_45420.jpg

1400_45420.jpg

1040 ms

1396_10533.jpg

1396_10533.jpg

1025 ms

1368_35393.jpg

1368_35393.jpg

931 ms

ukaz_306.jpg

ukaz_306.jpg

949 ms

line1.png

line1.png

945 ms

adv.png

adv.png

983 ms

logo1.png

logo1.png

910 ms

ico2.png

ico2.png

916 ms

advert.gif

advert.gif

113 ms

application2.js

application2.js

108 ms

1

1

113 ms

storage.html

storage.html

118 ms

MYRIADPRO-BOLDCOND.ttf

MYRIADPRO-BOLDCOND.ttf

518 ms

MYRIADPRO-BOLD.ttf

MYRIADPRO-BOLD.ttf

552 ms

MYRIADPRO-COND.ttf

MYRIADPRO-COND.ttf

536 ms

storage.js

storage.js

27 ms

MYRIADPRO-REGULAR.ttf

MYRIADPRO-REGULAR.ttf

457 ms

visits

visits

215 ms

5a96d51fdf3f61500d42dd170f9c9c63.css

5a96d51fdf3f61500d42dd170f9c9c63.css

32 ms

p

p

47 ms

buttons-dark.png

buttons-dark.png

28 ms

overlay.png

overlay.png

136 ms

loading.gif

loading.gif

259 ms

close.gif

close.gif

260 ms

SEO Factors

500w.ru SEO score

0

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 500w.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 500w.ru 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

500w.ru

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