Tools & Wizards About Us
wordspress.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% 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

wordspress.com

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

Page Load Speed

6.6 sec in total

First Response

29 ms

Resources Loaded

583 ms

Page Rendered

6 sec

wordspress.com screenshot

About Website

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

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

Visit wordspress.com

Key Findings

We analyzed Wordspress.com page load time and found that the first response time was 29 ms and then it took 6.6 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

wordspress.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

60/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

wordspress.com

29 ms

wordspress.com

20 ms

wordpress.com

23 ms

39 ms

bundle.js

118 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Wordspress.com, 60% (50 requests) were made to Wpcom.files.wordpress.com and 23% (19 requests) were made to S1.wp.com. The less responsive or slowest element that took the longest time to load (409 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 Wordspress.com 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 S Press images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 897 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 11 (14%)

Requests Now

79

After Optimization

68

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Word S 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

wordspress.com

wordspress.com

29 ms

wordspress.com

wordspress.com

20 ms

wordpress.com

wordpress.com

23 ms

39 ms

bundle.js

bundle.js

118 ms

115 ms

w.js

w.js

247 ms

bilmur.min.js

bilmur.min.js

14 ms

def-queue.js

def-queue.js

114 ms

group-1000004724.png

group-1000004724.png

368 ms

globe.svg

globe.svg

203 ms

cloud-logo.svg

cloud-logo.svg

200 ms

woo-logo.svg

woo-logo.svg

202 ms

bluehost-logo.svg

bluehost-logo.svg

196 ms

vip-logo.svg

vip-logo.svg

205 ms

time-logo.svg

time-logo.svg

225 ms

slack-logo.svg

slack-logo.svg

226 ms

disney-logo.svg

disney-logo.svg

227 ms

cnn-logo.svg

cnn-logo.svg

226 ms

salesforce-logo.svg

salesforce-logo.svg

223 ms

facebook-logo.svg

facebook-logo.svg

224 ms

condenast-logo.svg

condenast-logo.svg

267 ms

bloomberg-logo.svg

bloomberg-logo.svg

265 ms

jetpack-logo.svg

jetpack-logo.svg

332 ms

play-store-logo.png

play-store-logo.png

348 ms

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

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

370 ms

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

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

367 ms

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

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

354 ms

theme-11-2x-optimized.webp

theme-11-2x-optimized.webp

358 ms

theme-12-2x-optimized.webp

theme-12-2x-optimized.webp

361 ms

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

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

360 ms

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

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

361 ms

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

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

373 ms

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

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

367 ms

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

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

374 ms

theme-14-2x-optimized.webp

theme-14-2x-optimized.webp

368 ms

theme-15-2x-optimized.webp

theme-15-2x-optimized.webp

382 ms

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

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

377 ms

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

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

384 ms

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

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

376 ms

theme-16-2x-optimized.webp

theme-16-2x-optimized.webp

379 ms

theme-17-2x-optimized.webp

theme-17-2x-optimized.webp

381 ms

theme-18-2x-optimized.webp

theme-18-2x-optimized.webp

389 ms

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

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

384 ms

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

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

385 ms

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

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

386 ms

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

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

389 ms

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

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

390 ms

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

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

389 ms

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

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

390 ms

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

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

391 ms

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

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

393 ms

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

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

394 ms

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

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

393 ms

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

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

395 ms

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

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

394 ms

hey-world-1.png

hey-world-1.png

395 ms

newsletter-4-2x-optimized.webp

newsletter-4-2x-optimized.webp

409 ms

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

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

399 ms

400.woff

400.woff

260 ms

b.gif

b.gif

203 ms

w.js

w.js

77 ms

a8c-analytics.js

a8c-analytics.js

174 ms

179 ms

g.gif

g.gif

161 ms

g.gif

g.gif

160 ms

g.gif

g.gif

161 ms

t.gif

t.gif

161 ms

g.gif

g.gif

129 ms

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

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

79 ms

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

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

54 ms

video-4-2x-optimized.webp

video-4-2x-optimized.webp

53 ms

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

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

45 ms

store-4-2x-optimized.webp

store-4-2x-optimized.webp

45 ms

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

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

43 ms

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

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

49 ms

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

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

44 ms

support-2-2x-optimized.webp

support-2-2x-optimized.webp

41 ms

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

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

37 ms

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

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

44 ms

vip-logo.webp

vip-logo.webp

39 ms

logos-2x-optimized.webp

logos-2x-optimized.webp

40 ms

jetpack-splash.png

jetpack-splash.png

37 ms

Accessibility Review

wordspress.com 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

wordspress.com 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

wordspress.com 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 Wordspress.com 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 Wordspress.com 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

wordspress.com

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