Tools & Wizards About Us
root.bg screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

root.bg

root.bg by Nikolay Nikolov - статии и уроци за linux

Page Load Speed

3.3 sec in total

First Response

541 ms

Resources Loaded

1.9 sec

Page Rendered

897 ms

root.bg screenshot

About Website

Visit root.bg now to see the best up-to-date Root content for Bulgaria and also check out these interesting facts you probably never knew about root.bg

root.bg network - статии и уроци за linux, ръководства и съвети свързани с различни проблеми в областа на интернет технологиите и мрежите.

Visit root.bg

Key Findings

We analyzed Root.bg page load time and found that the first response time was 541 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

root.bg performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value1,320 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.351

31/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

root.bg

541 ms

autoptimize_48eee67e3270fd743578c0c7d8f97736.css

11 ms

font-awesome.min.css

4 ms

dashicons.min.css

46 ms

css

47 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 27% of them (13 requests) were addressed to the original Root.bg, 15% (7 requests) were made to Cdn.root.bg and 15% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (819 ms) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 994.4 kB (60%)

Content Size

1.7 MB

After Optimization

674.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Root.bg main page is 1.7 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. Javascripts take 707.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 62.8 kB

  • Original 79.8 kB
  • After minification 73.5 kB
  • After compression 17.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. 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 62.8 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 3.4 kB

  • Original 270.2 kB
  • After minification 266.7 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. Root images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 473.1 kB

  • Original 707.1 kB
  • After minification 695.0 kB
  • After compression 233.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 473.1 kB or 67% of the original size.

CSS Optimization

-74%

Potential reduce by 455.1 kB

  • Original 612.0 kB
  • After minification 611.3 kB
  • After compression 157.0 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. Root.bg needs all CSS files to be minified and compressed as it can save up to 455.1 kB or 74% of the original size.

Requests Breakdown

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

Requests Now

37

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

root.bg

root.bg

541 ms

autoptimize_48eee67e3270fd743578c0c7d8f97736.css

autoptimize_48eee67e3270fd743578c0c7d8f97736.css

11 ms

font-awesome.min.css

font-awesome.min.css

4 ms

dashicons.min.css

dashicons.min.css

46 ms

css

css

47 ms

css

css

48 ms

jwplayer.js

jwplayer.js

89 ms

analytics.js

analytics.js

35 ms

windows-10-logo.jpg

windows-10-logo.jpg

366 ms

wordpress-nginx.jpg

wordpress-nginx.jpg

350 ms

Screen-Shot-2016-02-12-at-14.07.02-1024x333.png

Screen-Shot-2016-02-12-at-14.07.02-1024x333.png

398 ms

Screen-Shot-2016-02-11-at-09.04.41.png

Screen-Shot-2016-02-11-at-09.04.41.png

423 ms

Screen-Shot-2016-02-11-at-09.15.38.png

Screen-Shot-2016-02-11-at-09.15.38.png

654 ms

687474703a2f2f656e67696e74726f6e2e636f6d2f6173736574732f6c6f676f2f456e67696e74726f6e5f4c6f676f5f3331367839385f32345f626c61636b2e706e67.png

687474703a2f2f656e67696e74726f6e2e636f6d2f6173736574732f6c6f676f2f456e67696e74726f6e5f4c6f676f5f3331367839385f32345f626c61636b2e706e67.png

426 ms

debian-jessie.jpg

debian-jessie.jpg

425 ms

simple-smile.png

simple-smile.png

114 ms

a

a

103 ms

devicepx-jetpack.js

devicepx-jetpack.js

105 ms

e-201609.js

e-201609.js

99 ms

autoptimize_1deb2a74a0f3f2aec13ae60e60fd4151.js

autoptimize_1deb2a74a0f3f2aec13ae60e60fd4151.js

101 ms

collect

collect

21 ms

s.gif

s.gif

15 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

10 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

224 ms

zhcz-_WihjSQC0oHJ9TCYMDdSZkkecOE1hvV7ZHvhyU.ttf

zhcz-_WihjSQC0oHJ9TCYMDdSZkkecOE1hvV7ZHvhyU.ttf

275 ms

IQHow_FEYlDC4Gzy_m8fcsBaWKZ57bY3RXgXH6dOjZ0.ttf

IQHow_FEYlDC4Gzy_m8fcsBaWKZ57bY3RXgXH6dOjZ0.ttf

304 ms

themify.woff

themify.woff

10 ms

MEz38VLIFL-t46JUtkIEgFvoNiiqtAOIyeIgKgNWTaM.ttf

MEz38VLIFL-t46JUtkIEgFvoNiiqtAOIyeIgKgNWTaM.ttf

552 ms

u-WUoqrET9fUeobQW7jkRSZ2oysoEQEeKwjgmXLRnTc.ttf

u-WUoqrET9fUeobQW7jkRSZ2oysoEQEeKwjgmXLRnTc.ttf

551 ms

DXI1ORHCpsQm3Vp6mXoaTY3LH2FgLjViKkqswU-xtII.ttf

DXI1ORHCpsQm3Vp6mXoaTY3LH2FgLjViKkqswU-xtII.ttf

552 ms

MTP_ySUJH_bn48VBG8sNSo3LH2FgLjViKkqswU-xtII.ttf

MTP_ySUJH_bn48VBG8sNSo3LH2FgLjViKkqswU-xtII.ttf

550 ms

k3k702ZOKiLJc3WVjuplzI3LH2FgLjViKkqswU-xtII.ttf

k3k702ZOKiLJc3WVjuplzI3LH2FgLjViKkqswU-xtII.ttf

551 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

220 ms

count.js

count.js

556 ms

atrk.js

atrk.js

461 ms

piwik.js

piwik.js

462 ms

watch.js

watch.js

819 ms

themify.builder.script.js

themify.builder.script.js

160 ms

rating_1_over.gif

rating_1_over.gif

76 ms

rating_2_over.gif

rating_2_over.gif

79 ms

g.gif

g.gif

53 ms

wow.js

wow.js

265 ms

atrk.gif

atrk.gif

33 ms

test.png

test.png

278 ms

animate.min.css

animate.min.css

37 ms

count-data.js

count-data.js

183 ms

advert.gif

advert.gif

92 ms

1

1

91 ms

Accessibility Review

root.bg accessibility score

82

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

[aria-*] attributes do not match their roles

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

Links do not have a discernible name

Best Practices

root.bg 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

SEO Factors

root.bg SEO score

100

Search Engine Optimization Advices

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

    BG

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

root.bg

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