Tools & Wizards About Us
wordpress.bg screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wordpress.bg

Blog Tool, Publishing Platform, and CMS | WordPress.org България

Page Load Speed

6.4 sec in total

First Response

225 ms

Resources Loaded

2.7 sec

Page Rendered

3.5 sec

wordpress.bg screenshot

About Website

Welcome to wordpress.bg homepage info - get ready to check Word Press best content right away, or after learning these important things about wordpress.bg

Софтуерът с отворен код, който можете да използвате, за да създадете красив сайт, блог или приложение.

Visit wordpress.bg

Key Findings

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

Performance Metrics

wordpress.bg performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

wordpress.bg

225 ms

bg.wordpress.org

890 ms

gtm.js

233 ms

wp-emoji-release.min.js

94 ms

dashicons.min.css

353 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Wordpress.bg, 30% (12 requests) were made to Bg.wordpress.org and 25% (10 requests) were made to S.w.org. The less responsive or slowest element that took the longest time to load (890 ms) relates to the external source Bg.wordpress.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.1 kB (6%)

Content Size

1.1 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wordpress.bg main page is 1.1 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. 60% of websites need less resources to load. Images take 967.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 55.0 kB

  • Original 70.1 kB
  • After minification 68.7 kB
  • After compression 15.1 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 55.0 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 8.6 kB

  • Original 967.6 kB
  • After minification 959.1 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. Word Press images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 178 B

  • Original 28.9 kB
  • After minification 28.9 kB
  • After compression 28.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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 1.3 kB

  • Original 80.3 kB
  • After minification 80.3 kB
  • After compression 78.9 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. Wordpress.bg has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (47%)

Requests Now

34

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wordpress.bg

wordpress.bg

225 ms

bg.wordpress.org

bg.wordpress.org

890 ms

gtm.js

gtm.js

233 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

94 ms

dashicons.min.css

dashicons.min.css

353 ms

admin-bar.min.css

admin-bar.min.css

348 ms

style.css

style.css

456 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

449 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

461 ms

css2

css2

491 ms

style.css

style.css

351 ms

style.css

style.css

446 ms

style.css

style.css

448 ms

view.min.js

view.min.js

446 ms

view-modal.min.js

view-modal.min.js

522 ms

load-scripts.php

load-scripts.php

584 ms

skip-link-focus-fix.min.js

skip-link-focus-fix.min.js

403 ms

view.js

view.js

504 ms

e-202239.js

e-202239.js

441 ms

analytics.js

analytics.js

276 ms

screen-themes.png

screen-themes.png

364 ms

http%3A%2F%2Fedno.bg%2F

http%3A%2F%2Fedno.bg%2F

824 ms

http%3A%2F%2Fbegach.com%2F

http%3A%2F%2Fbegach.com%2F

817 ms

http%3A%2F%2Fharmonica.bg%2F

http%3A%2F%2Fharmonica.bg%2F

816 ms

http%3A%2F%2Fzaednovchas.bg%2F

http%3A%2F%2Fzaednovchas.bg%2F

880 ms

mobile-themes.png

mobile-themes.png

628 ms

collage-min.jpg

collage-min.jpg

762 ms

icon-run-blue.svg

icon-run-blue.svg

628 ms

community-2.jpg

community-2.jpg

763 ms

steps.png

steps.png

631 ms

swag_col-2.png

swag_col-2.png

644 ms

collect

collect

223 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

361 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

421 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

423 ms

wARDj0u

wARDj0u

74 ms

collect

collect

57 ms

collect

collect

65 ms

collect

collect

78 ms

collect

collect

79 ms

Accessibility Review

wordpress.bg accessibility score

88

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

Best Practices

wordpress.bg best practices score

92

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

Page has valid source maps

SEO Factors

wordpress.bg SEO score

93

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

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

    BG

  • Encoding

    UTF-8

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

wordpress.bg

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