Tools & Wizards About Us
johnflorey.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

johnflorey.com

John Florey – A blog on my experiences, thoughts and views on business, current affairs, investment, blockchain and gemstones

Page Load Speed

5.5 sec in total

First Response

1.9 sec

Resources Loaded

3.1 sec

Page Rendered

468 ms

johnflorey.com screenshot

About Website

Click here to check amazing John Florey content. Otherwise, check out these important facts you probably never knew about johnflorey.com

A blog on my experiences, thoughts and views on business start-ups, current affairs, investment and art.

Visit johnflorey.com

Key Findings

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

Performance Metrics

johnflorey.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value700 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.185

66/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

johnflorey.com

1907 ms

wp-emoji-release.min.js

339 ms

styles.css

341 ms

mediaelementplayer.min.css

344 ms

wp-mediaelement.min.css

342 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 56% of them (37 requests) were addressed to the original Johnflorey.com, 12% (8 requests) were made to I0.wp.com and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Johnflorey.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 91.6 kB (9%)

Content Size

973.2 kB

After Optimization

881.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Johnflorey.com main page is 973.2 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. 65% of websites need less resources to load. Images take 634.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 75.6 kB

  • Original 87.5 kB
  • After minification 73.8 kB
  • After compression 11.9 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. This page needs HTML code to be minified as it can gain 13.7 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 75.6 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 86 B

  • Original 634.8 kB
  • After minification 634.7 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. John Florey images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 6.7 kB

  • Original 195.0 kB
  • After minification 195.0 kB
  • After compression 188.3 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

-16%

Potential reduce by 9.2 kB

  • Original 55.9 kB
  • After minification 55.6 kB
  • After compression 46.7 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. Johnflorey.com needs all CSS files to be minified and compressed as it can save up to 9.2 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (65%)

Requests Now

57

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of John Florey. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

johnflorey.com

johnflorey.com

1907 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

339 ms

styles.css

styles.css

341 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

344 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

342 ms

instag-slider.css

instag-slider.css

345 ms

wp-featherlight.min.css

wp-featherlight.min.css

344 ms

style.css

style.css

422 ms

components.css

components.css

424 ms

font-awesome.css

font-awesome.css

431 ms

css

css

18 ms

css

css

30 ms

style.css

style.css

513 ms

style-responsive.css

style-responsive.css

432 ms

custom.css

custom.css

435 ms

jetpack.css

jetpack.css

506 ms

jquery.js

jquery.js

592 ms

jquery-migrate.min.js

jquery-migrate.min.js

517 ms

tiled-gallery.js

tiled-gallery.js

517 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

521 ms

cleantalk_nocache.js

cleantalk_nocache.js

704 ms

post-like.min.js

post-like.min.js

702 ms

load-posts.js

load-posts.js

703 ms

photon.js

photon.js

703 ms

jquery.form.min.js

jquery.form.min.js

703 ms

scripts.js

scripts.js

742 ms

devicepx-jetpack.js

devicepx-jetpack.js

4 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

742 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

741 ms

gprofiles.js

gprofiles.js

5 ms

wpgroho.js

wpgroho.js

741 ms

wpFeatherlight.pkgd.min.js

wpFeatherlight.pkgd.min.js

741 ms

components.js

components.js

812 ms

smooth-scroll.js

smooth-scroll.js

811 ms

masonry.min.js

masonry.min.js

811 ms

core.js

core.js

810 ms

wp-embed.min.js

wp-embed.min.js

810 ms

e-202410.js

e-202410.js

4 ms

gprofiles.js

gprofiles.js

13 ms

analytics.js

analytics.js

92 ms

UK-For-Sale-Property-Boards-download.jpeg

UK-For-Sale-Property-Boards-download.jpeg

125 ms

RUBY-RING-MARA.jpg

RUBY-RING-MARA.jpg

449 ms

btn_liprofile_blue_80x15.png

btn_liprofile_blue_80x15.png

107 ms

investing.jpg

investing.jpg

104 ms

blockchain-3438501__480-Free-Image.jpg

blockchain-3438501__480-Free-Image.jpg

101 ms

RUBY-RING-MARA.jpg

RUBY-RING-MARA.jpg

472 ms

jf-logo.png

jf-logo.png

172 ms

arrow.svg

arrow.svg

251 ms

1.68-Sri-Lankan-Blue-Heated-Sapphire-.jpg

1.68-Sri-Lankan-Blue-Heated-Sapphire-.jpg

278 ms

Hotel-Market-Barcelona-Nov-2019-HI551882475.jpg

Hotel-Market-Barcelona-Nov-2019-HI551882475.jpg

103 ms

2015-09-01-12.39.41.jpg

2015-09-01-12.39.41.jpg

242 ms

UK-For-Sale-Property-Boards-download.jpeg

UK-For-Sale-Property-Boards-download.jpeg

146 ms

1.68-Sri-Lankan-Blue-Heated-Sapphire-.jpg

1.68-Sri-Lankan-Blue-Heated-Sapphire-.jpg

250 ms

SlGVmQWMvZQIdix7AFxXkHNSaw.woff

SlGVmQWMvZQIdix7AFxXkHNSaw.woff

35 ms

SlGWmQWMvZQIdix7AFxXmMh3eDs1YQ.woff

SlGWmQWMvZQIdix7AFxXmMh3eDs1YQ.woff

36 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtU.woff

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtU.woff

37 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtU.woff

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtU.woff

37 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtU.woff

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtU.woff

39 ms

elegant.woff

elegant.woff

262 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

348 ms

collect

collect

87 ms

show

show

68 ms

show

show

68 ms

js

js

104 ms

UK-For-Sale-Property-Boards-download.jpeg

UK-For-Sale-Property-Boards-download.jpeg

145 ms

1.68-Sri-Lankan-Blue-Heated-Sapphire-.jpg

1.68-Sri-Lankan-Blue-Heated-Sapphire-.jpg

265 ms

Accessibility Review

johnflorey.com accessibility score

80

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

johnflorey.com best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

johnflorey.com SEO score

68

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Document doesn't have a valid hreflang

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

High

Tap targets are not sized appropriately

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

johnflorey.com

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