Tools & Wizards About Us
wordpress.com.br screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wordpress.com.br

WordPress.com: Build a Site, Sell Your Stuff, Start a Blog & More

Page Load Speed

5.3 sec in total

First Response

102 ms

Resources Loaded

565 ms

Page Rendered

4.6 sec

wordpress.com.br screenshot

About Website

Click here to check amazing Word Press content. Otherwise, check out these important facts you probably never knew about wordpress.com.br

Build a site, sell online, earn with your content, and more

Visit wordpress.com.br

Key Findings

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

Performance Metrics

wordpress.com.br performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

wordpress.com.br

102 ms

wordpress.com.br

21 ms

wordpress.com

28 ms

32 ms

bundle.js

27 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Wordpress.com.br, 59% (50 requests) were made to Wpcom.files.wordpress.com and 22% (19 requests) were made to S1.wp.com. The less responsive or slowest element that took the longest time to load (309 ms) relates to the external source Wpcom.files.wordpress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 343.7 kB (3%)

Content Size

10.8 MB

After Optimization

10.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wordpress.com.br main page is 10.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. Only a small number of websites need less resources to load. Images take 10.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 232.3 kB

  • Original 289.9 kB
  • After minification 278.2 kB
  • After compression 57.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 232.3 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 110.5 kB

  • Original 10.4 MB
  • After minification 10.3 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. Word Press images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 899 B

  • Original 108.6 kB
  • After minification 108.6 kB
  • After compression 107.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.

Requests Breakdown

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

Requests Now

81

After Optimization

68

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 81 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 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

wordpress.com.br

wordpress.com.br

102 ms

wordpress.com.br

wordpress.com.br

21 ms

wordpress.com

wordpress.com

28 ms

32 ms

bundle.js

bundle.js

27 ms

196 ms

w.js

w.js

27 ms

bilmur.min.js

bilmur.min.js

19 ms

def-queue.js

def-queue.js

26 ms

group-1000004724.png

group-1000004724.png

210 ms

globe.svg

globe.svg

159 ms

cloud-logo.svg

cloud-logo.svg

157 ms

woo-logo.svg

woo-logo.svg

173 ms

bluehost-logo.svg

bluehost-logo.svg

158 ms

vip-logo.svg

vip-logo.svg

177 ms

time-logo.svg

time-logo.svg

176 ms

slack-logo.svg

slack-logo.svg

181 ms

disney-logo.svg

disney-logo.svg

195 ms

cnn-logo.svg

cnn-logo.svg

182 ms

salesforce-logo.svg

salesforce-logo.svg

196 ms

facebook-logo.svg

facebook-logo.svg

205 ms

condenast-logo.svg

condenast-logo.svg

207 ms

bloomberg-logo.svg

bloomberg-logo.svg

210 ms

jetpack-logo.svg

jetpack-logo.svg

257 ms

play-store-logo.png

play-store-logo.png

196 ms

theme-1-2x-2-optimized.webp

theme-1-2x-2-optimized.webp

282 ms

theme-2-2x-2-optimized.webp

theme-2-2x-2-optimized.webp

278 ms

theme-3-2x-3-optimized.webp

theme-3-2x-3-optimized.webp

213 ms

theme-11-2x-optimized.webp

theme-11-2x-optimized.webp

269 ms

theme-12-2x-optimized.webp

theme-12-2x-optimized.webp

269 ms

theme-3-2-2x-optimized.webp

theme-3-2-2x-optimized.webp

273 ms

theme-19-2-2x-optimized.webp

theme-19-2-2x-optimized.webp

274 ms

theme-4-2x-2-optimized.webp

theme-4-2x-2-optimized.webp

283 ms

theme-5-2x-2-optimized.webp

theme-5-2x-2-optimized.webp

275 ms

theme-6-2x-2-optimized.webp

theme-6-2x-2-optimized.webp

280 ms

theme-14-2x-optimized.webp

theme-14-2x-optimized.webp

278 ms

theme-15-2x-optimized.webp

theme-15-2x-optimized.webp

286 ms

theme-7-2x-2-optimized.webp

theme-7-2x-2-optimized.webp

285 ms

theme-8-2x-2-optimized.webp

theme-8-2x-2-optimized.webp

292 ms

theme-9-2x-2-optimized.webp

theme-9-2x-2-optimized.webp

290 ms

theme-16-2x-optimized.webp

theme-16-2x-optimized.webp

288 ms

theme-17-2x-optimized.webp

theme-17-2x-optimized.webp

288 ms

theme-18-2x-optimized.webp

theme-18-2x-optimized.webp

293 ms

theme-mobile-1-2x-optimized.webp

theme-mobile-1-2x-optimized.webp

290 ms

theme-mobile-2-2x-optimized.webp

theme-mobile-2-2x-optimized.webp

299 ms

theme-mobile-3-2x-optimized.webp

theme-mobile-3-2x-optimized.webp

292 ms

theme-mobile-4-2x-optimized.webp

theme-mobile-4-2x-optimized.webp

293 ms

theme-mobile-5-2x-optimized.webp

theme-mobile-5-2x-optimized.webp

296 ms

theme-mobile-6-2x-optimized.webp

theme-mobile-6-2x-optimized.webp

293 ms

theme-mobile-7-2x-optimized.webp

theme-mobile-7-2x-optimized.webp

295 ms

theme-mobile-8-2x-optimized.webp

theme-mobile-8-2x-optimized.webp

294 ms

theme-mobile-9-2x-optimized.webp

theme-mobile-9-2x-optimized.webp

296 ms

theme-mobile-10-2x-optimized.webp

theme-mobile-10-2x-optimized.webp

297 ms

theme-mobile-11-2x-optimized.webp

theme-mobile-11-2x-optimized.webp

299 ms

theme-mobile-12-2x-optimized.webp

theme-mobile-12-2x-optimized.webp

300 ms

theme-mobile-13-2x-optimized.webp

theme-mobile-13-2x-optimized.webp

300 ms

hey-world-1.png

hey-world-1.png

299 ms

newsletter-4-2x-optimized.webp

newsletter-4-2x-optimized.webp

309 ms

newsletter-4-m-2x-optimized.webp

newsletter-4-m-2x-optimized.webp

304 ms

400.woff

400.woff

193 ms

b.gif

b.gif

159 ms

w.js

w.js

57 ms

a8c-analytics.js

a8c-analytics.js

147 ms

149 ms

g.gif

g.gif

127 ms

g.gif

g.gif

111 ms

g.gif

g.gif

128 ms

t.gif

t.gif

128 ms

g.gif

g.gif

117 ms

link-in-bio-4-2x-optimized.webp

link-in-bio-4-2x-optimized.webp

148 ms

link-in-bio-4-m-2x-optimized.webp

link-in-bio-4-m-2x-optimized.webp

110 ms

t.gif

t.gif

66 ms

t.gif

t.gif

66 ms

video-4-2x-optimized.webp

video-4-2x-optimized.webp

98 ms

video-4-m-2x-optimized.webp

video-4-m-2x-optimized.webp

38 ms

store-4-2x-optimized.webp

store-4-2x-optimized.webp

39 ms

store-4-m-2x-optimized.webp

store-4-m-2x-optimized.webp

35 ms

course-4-2x-1-optimized.webp

course-4-2x-1-optimized.webp

41 ms

course-4-m-2x-1-optimized.webp

course-4-m-2x-1-optimized.webp

36 ms

support-2-2x-optimized.webp

support-2-2x-optimized.webp

36 ms

support-2-m-2x-optimized.webp

support-2-m-2x-optimized.webp

33 ms

built-by-2-2x-1-optimized.webp

built-by-2-2x-1-optimized.webp

37 ms

vip-logo.webp

vip-logo.webp

32 ms

logos-2x-optimized.webp

logos-2x-optimized.webp

33 ms

jetpack-splash.png

jetpack-splash.png

29 ms

Accessibility Review

wordpress.com.br accessibility score

84

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 input fields do not have accessible names

High

[role]s are not contained by their required parent element

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

wordpress.com.br 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

SEO Factors

wordpress.com.br 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

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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: