Tools & Wizards About Us
wordperess.com screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wordperess.com

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

Page Load Speed

4.3 sec in total

First Response

13 ms

Resources Loaded

342 ms

Page Rendered

3.9 sec

wordperess.com screenshot

About Website

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

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

Visit wordperess.com

Key Findings

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

Performance Metrics

wordperess.com performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value550 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

wordperess.com

13 ms

wordperess.com

21 ms

wordpress.com

32 ms

30 ms

css2

47 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Wordperess.com, 56% (27 requests) were made to Wordpress.com and 15% (7 requests) were made to Pixel.wp.com. The less responsive or slowest element that took the longest time to load (184 ms) relates to the external source Wordpress.com.

Page Optimization Overview & Recommendations

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

Content Size

5.0 MB

After Optimization

4.7 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wordperess.com main page is 5.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 238.8 kB

  • Original 350.6 kB
  • After minification 346.3 kB
  • After compression 111.8 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 238.8 kB or 68% of the original size.

Image Optimization

-3%

Potential reduce by 121.4 kB

  • Original 4.6 MB
  • After minification 4.5 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 Peress 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 11 (26%)

Requests Now

42

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

wordperess.com

wordperess.com

13 ms

wordperess.com

wordperess.com

21 ms

wordpress.com

wordpress.com

32 ms

30 ms

css2

css2

47 ms

bundle.js

bundle.js

32 ms

31 ms

w.js

w.js

32 ms

bilmur.min.js

bilmur.min.js

19 ms

def-queue.js

def-queue.js

30 ms

globe-blue.svg

globe-blue.svg

124 ms

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

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

184 ms

g.gif

g.gif

137 ms

a8c-analytics.js

a8c-analytics.js

144 ms

147 ms

lohp-i3-hero-2x.png

lohp-i3-hero-2x.png

113 ms

vip-logo-2.webp

vip-logo-2.webp

113 ms

g.gif

g.gif

124 ms

g.gif

g.gif

128 ms

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

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

141 ms

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

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

125 ms

theme-11-2x-optimized.webp

theme-11-2x-optimized.webp

129 ms

theme-12-2x-optimized.webp

theme-12-2x-optimized.webp

133 ms

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

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

133 ms

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

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

134 ms

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

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

163 ms

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

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

140 ms

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

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

165 ms

theme-14-2x-optimized.webp

theme-14-2x-optimized.webp

161 ms

theme-15-2x-optimized.webp

theme-15-2x-optimized.webp

172 ms

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

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

164 ms

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

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

166 ms

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

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

163 ms

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

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

166 ms

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

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

170 ms

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

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

166 ms

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

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

167 ms

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

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

167 ms

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

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

168 ms

b.gif

b.gif

59 ms

t.gif

t.gif

60 ms

i7dPIFZifjKcF5UAWdDRUEY.ttf

i7dPIFZifjKcF5UAWdDRUEY.ttf

71 ms

group-1000004724.png

group-1000004724.png

82 ms

t.gif

t.gif

42 ms

t.gif

t.gif

42 ms

play-store-logo.png

play-store-logo.png

62 ms

lohp-i3-hero-2x.png

lohp-i3-hero-2x.png

59 ms

vip-logo-2.webp

vip-logo-2.webp

60 ms

Accessibility Review

wordperess.com accessibility score

91

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

Links do not have a discernible name

Best Practices

wordperess.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

wordperess.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 Wordperess.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 Wordperess.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

wordperess.com

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