Tools & Wizards About Us
kenpienaar.wordpress.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

kenpienaar.wordpress.com

Ken Pienaar's Memoirs – Memoirs of a PR man from South Africa

Page Load Speed

629 ms in total

First Response

7 ms

Resources Loaded

546 ms

Page Rendered

76 ms

kenpienaar.wordpress.com screenshot

About Website

Click here to check amazing Ken Pienaar Word PR Ess content for United States. Otherwise, check out these important facts you probably never knew about kenpienaar.wordpress.com

The memoirs of journalist-turned-PR man who lived through the apartheid era and into the new South Africa. Ken Pienaar was an independent writer who believed in the power of PR to promote a business. ...

Visit kenpienaar.wordpress.com

Key Findings

We analyzed Kenpienaar.wordpress.com page load time and found that the first response time was 7 ms and then it took 622 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

kenpienaar.wordpress.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.167

71/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

kenpienaar.wordpress.com

7 ms

kenpienaar.wordpress.com

236 ms

webfont.js

74 ms

101 ms

105 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Kenpienaar.wordpress.com, 25% (9 requests) were made to S2.wp.com and 19% (7 requests) were made to Fonts.wp.com. The less responsive or slowest element that took the longest time to load (236 ms) belongs to the original domain Kenpienaar.wordpress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 60.5 kB (30%)

Content Size

202.5 kB

After Optimization

141.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kenpienaar.wordpress.com main page is 202.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. HTML takes 83.1 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 59.8 kB

  • Original 83.1 kB
  • After minification 82.2 kB
  • After compression 23.3 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 59.8 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 8.2 kB
  • After minification 8.2 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. Ken Pienaar Word PR Ess images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 604 B

  • Original 70.8 kB
  • After minification 70.8 kB
  • After compression 70.2 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

-0%

Potential reduce by 165 B

  • Original 40.4 kB
  • After minification 40.4 kB
  • After compression 40.2 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. Kenpienaar.wordpress.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (67%)

Requests Now

27

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kenpienaar.wordpress.com

kenpienaar.wordpress.com

7 ms

kenpienaar.wordpress.com

kenpienaar.wordpress.com

236 ms

webfont.js

webfont.js

74 ms

101 ms

105 ms

104 ms

115 ms

verbum-comments.css

verbum-comments.css

114 ms

block-editor.css

block-editor.css

117 ms

114 ms

css

css

135 ms

125 ms

107 ms

125 ms

hovercards.min.js

hovercards.min.js

115 ms

wpgroho.js

wpgroho.js

111 ms

124 ms

w.js

w.js

124 ms

css

css

64 ms

global-print.css

global-print.css

1 ms

conf

conf

163 ms

ga.js

ga.js

65 ms

wpcom-gray-white.png

wpcom-gray-white.png

42 ms

g.gif

g.gif

103 ms

112 ms

wpcom-mark.svg

wpcom-mark.svg

49 ms

g.gif

g.gif

99 ms

g.gif

g.gif

99 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmYWRl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmYWRl.woff

73 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmYWRl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmYWRl.woff

65 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OmYWRl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OmYWRl.woff

73 ms

EJRVQgYoZZY2vCFuvAFYzrk.woff

EJRVQgYoZZY2vCFuvAFYzrk.woff

73 ms

EJRSQgYoZZY2vCFuvAnt66qcVy0.woff

EJRSQgYoZZY2vCFuvAnt66qcVy0.woff

73 ms

EJRTQgYoZZY2vCFuvAFT_rO1dA.woff

EJRTQgYoZZY2vCFuvAFT_rO1dA.woff

73 ms

EJRQQgYoZZY2vCFuvAFT9gaQZyffpg.woff

EJRQQgYoZZY2vCFuvAFT9gaQZyffpg.woff

73 ms

__utm.gif

__utm.gif

35 ms

Accessibility Review

kenpienaar.wordpress.com accessibility score

96

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

Best Practices

kenpienaar.wordpress.com best practices score

75

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

kenpienaar.wordpress.com SEO score

100

Search Engine Optimization Advices

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 Kenpienaar.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 Kenpienaar.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

kenpienaar.wordpress.com

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