Tools & Wizards About Us
seozalex.ru screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

seozalex.ru

Записки Костромского SEO Зайца

Page Load Speed

4.5 sec in total

First Response

716 ms

Resources Loaded

2.9 sec

Page Rendered

828 ms

seozalex.ru screenshot

About Website

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

Модуль ДЛЕ парсер программы ТВ с mail.ru, 20 бэков PR 8 и PR 9 в одной упаковке, Как повысить Alexa

Visit seozalex.ru

Key Findings

We analyzed Seozalex.ru page load time and found that the first response time was 716 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 65% of websites can load faster.

Performance Metrics

seozalex.ru performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

54/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

seozalex.ru

716 ms

style.css

414 ms

hc_reset.css_ver=3.5.1

467 ms

hc_tpl_fonts.css_ver=3.5.1

443 ms

css

48 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 51% of them (46 requests) were addressed to the original Seozalex.ru, 11% (10 requests) were made to Facebook.com and 10% (9 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (868 ms) belongs to the original domain Seozalex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 249.4 kB (33%)

Content Size

767.3 kB

After Optimization

517.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 181.9 kB

  • Original 225.7 kB
  • After minification 224.4 kB
  • After compression 43.7 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 181.9 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 8.9 kB

  • Original 455.8 kB
  • After minification 446.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. SEO Zalex images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 47.5 kB

  • Original 72.2 kB
  • After minification 71.5 kB
  • After compression 24.7 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 47.5 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 11.1 kB

  • Original 13.6 kB
  • After minification 10.4 kB
  • After compression 2.5 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. Seozalex.ru needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (38%)

Requests Now

81

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

seozalex.ru

seozalex.ru

716 ms

style.css

style.css

414 ms

hc_reset.css_ver=3.5.1

hc_reset.css_ver=3.5.1

467 ms

hc_tpl_fonts.css_ver=3.5.1

hc_tpl_fonts.css_ver=3.5.1

443 ms

css

css

48 ms

hcmodalbasic.css_ver=3.5.1

hcmodalbasic.css_ver=3.5.1

450 ms

front.css_ver=1.1.0

front.css_ver=1.1.0

451 ms

wp-syntax.css_ver=1.0

wp-syntax.css_ver=1.0

441 ms

pagenavi-css.css_ver=2.70

pagenavi-css.css_ver=2.70

564 ms

pin_admin.js_ver=3.5.1

pin_admin.js_ver=3.5.1

648 ms

jquery.min.js

jquery.min.js

16 ms

pin_frontend.js_ver=3.5.1

pin_frontend.js_ver=3.5.1

664 ms

jquery.simplemodal.1.4.3.min.js_ver=3.5.1

jquery.simplemodal.1.4.3.min.js_ver=3.5.1

661 ms

waypoints.min.js_ver=3.5.1

waypoints.min.js_ver=3.5.1

627 ms

lightbox.js_ver=3.3

lightbox.js_ver=3.3

630 ms

flowplayer-3.2.6.min.js_ver=3.0

flowplayer-3.2.6.min.js_ver=3.0

716 ms

flowplayer.ipad-3.2.2.min.js_ver=3.0

flowplayer.ipad-3.2.2.min.js_ver=3.0

782 ms

placeholder.jquery.js_ver=3.0

placeholder.jquery.js_ver=3.0

782 ms

widgets.js

widgets.js

136 ms

all.js

all.js

132 ms

plusone.js

plusone.js

100 ms

FB.Share

FB.Share

57 ms

in.js

in.js

68 ms

all.js

all.js

77 ms

templatelite.js

templatelite.js

868 ms

pinit.js

pinit.js

55 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

46 ms

secureAnonymousFramework

secureAnonymousFramework

34 ms

PinExt.png

PinExt.png

33 ms

phphubru

phphubru

84 ms

bg_repeat.jpg

bg_repeat.jpg

305 ms

spacer.gif

spacer.gif

174 ms

televizor-300x225.jpg

televizor-300x225.jpg

179 ms

PandaandPenguin-300x199.jpg

PandaandPenguin-300x199.jpg

305 ms

1326633782_demotiv-300x218.jpg

1326633782_demotiv-300x218.jpg

327 ms

icon_smile.gif

icon_smile.gif

174 ms

1323846043_demotiv-300x125.jpg

1323846043_demotiv-300x125.jpg

475 ms

avatar-300x147.jpg

avatar-300x147.jpg

481 ms

1322543517_demotiv-260x300.jpg

1322543517_demotiv-260x300.jpg

486 ms

77 ms

78 ms

opacity.css

opacity.css

433 ms

xd_arbiter.php

xd_arbiter.php

82 ms

xd_arbiter.php

xd_arbiter.php

140 ms

bg_top.jpg

bg_top.jpg

170 ms

bg_btm.jpg

bg_btm.jpg

459 ms

bg_base_repeat.jpg

bg_base_repeat.jpg

503 ms

bg_header.jpg

bg_header.jpg

489 ms

bg_container_top.jpg

bg_container_top.jpg

460 ms

bg_post_top.png

bg_post_top.png

178 ms

bg_post_repeat.png

bg_post_repeat.png

458 ms

icon_category.jpg

icon_category.jpg

453 ms

icon_tags.jpg

icon_tags.jpg

482 ms

icon_comment.jpg

icon_comment.jpg

494 ms

bg_post_btm.png

bg_post_btm.png

511 ms

pinit_main.js

pinit_main.js

28 ms

cvp_v=RklPWURsQ2Y4T018OXxzaW1wbGVfYmxhY2t8fDQwMTAwMTB8aHR0cDovLywsLCx0ciw3LDA%3D.html

cvp_v=RklPWURsQ2Y4T018OXxzaW1wbGVfYmxhY2t8fDQwMTAwMTB8aHR0cDovLywsLCx0ciw3LDA%3D.html

557 ms

2_120x120_18.swf.js

2_120x120_18.swf.js

258 ms

bg_sb_arrow1.jpg

bg_sb_arrow1.jpg

326 ms

bg_sb_arrow2.jpg

bg_sb_arrow2.jpg

323 ms

bg_footer.jpg

bg_footer.jpg

322 ms

hit

hit

301 ms

admin-ajax.php

admin-ajax.php

525 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

99 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

45 ms

fastbutton

fastbutton

77 ms

peePin.png

peePin.png

193 ms

pin_small.png

pin_small.png

195 ms

xd_arbiter.php

xd_arbiter.php

64 ms

postmessageRelay

postmessageRelay

144 ms

rs=AGLTcCNFg9Lxr6A_1qJE1FafaQPPaU_lFQ

rs=AGLTcCNFg9Lxr6A_1qJE1FafaQPPaU_lFQ

35 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ru.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ru.html

213 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

92 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

110 ms

like.php

like.php

161 ms

like.php

like.php

160 ms

like.php

like.php

233 ms

swfobject.js

swfobject.js

249 ms

like.php

like.php

226 ms

like.php

like.php

223 ms

like.php

like.php

225 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

221 ms

like.php

like.php

205 ms

like.php

like.php

208 ms

hit

hit

201 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

193 ms

rpc:shindig_random.js

rpc:shindig_random.js

172 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

267 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

277 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

3 ms

jot.html

jot.html

34 ms

Accessibility Review

seozalex.ru accessibility score

62

Accessibility Issues

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

Form elements do not have associated labels

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

seozalex.ru best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

seozalex.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

Document uses plugins

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Seozalex.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Seozalex.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

seozalex.ru

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