Tools & Wizards About Us
so.wordpress.com screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

so.wordpress.com

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

Page Load Speed

5.8 sec in total

First Response

7 ms

Resources Loaded

1.5 sec

Page Rendered

4.3 sec

so.wordpress.com screenshot

About Website

Visit so.wordpress.com now to see the best up-to-date So Word Press content for United States and also check out these interesting facts you probably never knew about so.wordpress.com

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

Visit so.wordpress.com

Key Findings

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

so.wordpress.com performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value680 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

so.wordpress.com

7 ms

wordpress.com

33 ms

31 ms

css2

46 ms

bundle.js

32 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original So.wordpress.com, 57% (31 requests) were made to Wordpress.com and 13% (7 requests) were made to Pixel.wp.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Wordpress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 364.7 kB (7%)

Content Size

5.1 MB

After Optimization

4.8 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of So.wordpress.com main page is 5.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 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 241.5 kB

  • Original 353.8 kB
  • After minification 349.3 kB
  • After compression 112.2 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 241.5 kB or 68% of the original size.

Image Optimization

-3%

Potential reduce by 122.6 kB

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

JavaScript Optimization

-1%

Potential reduce by 523 B

  • Original 61.2 kB
  • After minification 61.2 kB
  • After compression 60.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 (28%)

Requests Now

46

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of So 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 6 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

so.wordpress.com

so.wordpress.com

7 ms

wordpress.com

wordpress.com

33 ms

31 ms

css2

css2

46 ms

bundle.js

bundle.js

32 ms

33 ms

w.js

w.js

33 ms

bilmur.min.js

bilmur.min.js

19 ms

def-queue.js

def-queue.js

32 ms

group-1000004724.png

group-1000004724.png

150 ms

globe-blue.svg

globe-blue.svg

141 ms

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

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

1437 ms

g.gif

g.gif

161 ms

a8c-analytics.js

a8c-analytics.js

160 ms

164 ms

lohp-i3-hero-2x.png

lohp-i3-hero-2x.png

127 ms

left-line-3x.png

left-line-3x.png

128 ms

wp-migration-icon-2x.png

wp-migration-icon-2x.png

145 ms

g.gif

g.gif

147 ms

g.gif

g.gif

148 ms

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

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

1122 ms

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

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

181 ms

theme-11-2x-optimized.webp

theme-11-2x-optimized.webp

187 ms

theme-12-2x-optimized.webp

theme-12-2x-optimized.webp

190 ms

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

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

192 ms

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

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

244 ms

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

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

311 ms

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

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

533 ms

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

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

791 ms

theme-14-2x-optimized.webp

theme-14-2x-optimized.webp

326 ms

theme-15-2x-optimized.webp

theme-15-2x-optimized.webp

1111 ms

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

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

538 ms

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

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

728 ms

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

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

686 ms

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

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

828 ms

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

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

934 ms

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

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

936 ms

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

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

946 ms

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

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

1075 ms

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

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

972 ms

400.woff

400.woff

112 ms

b.gif

b.gif

64 ms

t.gif

t.gif

64 ms

i7dPIFZifjKcF5UAWdDRUEY.ttf

i7dPIFZifjKcF5UAWdDRUEY.ttf

214 ms

group-1000004724.png

group-1000004724.png

875 ms

t.gif

t.gif

60 ms

t.gif

t.gif

60 ms

play-store-logo.png

play-store-logo.png

869 ms

lohp-i3-hero-2x.png

lohp-i3-hero-2x.png

865 ms

left-line-3x.png

left-line-3x.png

869 ms

vip-logo-2.webp

vip-logo-2.webp

927 ms

migration-image-right-side-_1_optimized.png

migration-image-right-side-_1_optimized.png

883 ms

right-line-3x.png

right-line-3x.png

898 ms

wp-migration-icon-2x.png

wp-migration-icon-2x.png

902 ms

Accessibility Review

so.wordpress.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

[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

so.wordpress.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

so.wordpress.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 So.wordpress.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 So.wordpress.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

so.wordpress.com

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