Tools & Wizards About Us
johnbrianking.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

johnbrianking.com

John Brian King

Page Load Speed

2.9 sec in total

First Response

595 ms

Resources Loaded

1.9 sec

Page Rendered

352 ms

johnbrianking.com screenshot

About Website

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

Photography, writing, and film by John Brian King

Visit johnbrianking.com

Key Findings

We analyzed Johnbrianking.com page load time and found that the first response time was 595 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

johnbrianking.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value670 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.2 s

6/100

10%

Network Requests Diagram

johnbrianking.com

595 ms

cargo.apicore.package.js

268 ms

apipackage

377 ms

javascript

209 ms

stylesheet

210 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 19% of them (13 requests) were addressed to the original Johnbrianking.com, 66% (46 requests) were made to Payload.cargocollective.com and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (667 ms) relates to the external source Payload.cargocollective.com.

Page Optimization Overview & Recommendations

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

Content Size

2.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Johnbrianking.com main page is 2.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. 45% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 129.8 kB

  • Original 139.5 kB
  • After minification 130.5 kB
  • After compression 9.7 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 129.8 kB or 93% of the original size.

Image Optimization

-2%

Potential reduce by 37.8 kB

  • Original 1.7 MB
  • After minification 1.7 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. John Brian King images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 5.0 kB

  • Original 131.5 kB
  • After minification 131.5 kB
  • After compression 126.5 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

-15%

Potential reduce by 891 B

  • Original 5.8 kB
  • After minification 5.8 kB
  • After compression 5.0 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. Johnbrianking.com needs all CSS files to be minified and compressed as it can save up to 891 B or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (10%)

Requests Now

69

After Optimization

62

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of John Brian King. 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 as a result speed up the page load time.

Network Requests Diagram

johnbrianking.com

johnbrianking.com

595 ms

cargo.apicore.package.js

cargo.apicore.package.js

268 ms

apipackage

apipackage

377 ms

javascript

javascript

209 ms

stylesheet

stylesheet

210 ms

global.css

global.css

290 ms

js

js

76 ms

webfont.js

webfont.js

81 ms

arrow-up.svg

arrow-up.svg

94 ms

prt_200x200_1600572249.jpg

prt_200x200_1600572249.jpg

186 ms

index.svg

index.svg

94 ms

arrow-down.svg

arrow-down.svg

95 ms

prt_200x200_1576544044.jpg

prt_200x200_1576544044.jpg

260 ms

prt_200x200_1485190687.jpg

prt_200x200_1485190687.jpg

285 ms

prt_200x200_1609562291.jpg

prt_200x200_1609562291.jpg

257 ms

prt_200x200_1485190116.jpg

prt_200x200_1485190116.jpg

266 ms

prt_200x200_1699983853.jpg

prt_200x200_1699983853.jpg

300 ms

prt_200x200_1630595127.jpg

prt_200x200_1630595127.jpg

277 ms

prt_200x200_1646371784.jpg

prt_200x200_1646371784.jpg

304 ms

prt_200x200_1657142254.jpg

prt_200x200_1657142254.jpg

319 ms

prt_200x200_1718945847.JPG

prt_200x200_1718945847.JPG

337 ms

prt_200x200_1728604940.JPG

prt_200x200_1728604940.JPG

563 ms

prt_200x200_1718942784.jpg

prt_200x200_1718942784.jpg

354 ms

prt_200x200_1726261751.jpg

prt_200x200_1726261751.jpg

319 ms

prt_200x200_1730128538.jpg

prt_200x200_1730128538.jpg

364 ms

prt_200x200_1714671211.jpg

prt_200x200_1714671211.jpg

381 ms

prt_200x200_1726186853.jpg

prt_200x200_1726186853.jpg

343 ms

prt_200x200_1718942889.jpg

prt_200x200_1718942889.jpg

391 ms

prt_200x200_1723171284.jpg

prt_200x200_1723171284.jpg

408 ms

prt_200x200_1719293711.jpg

prt_200x200_1719293711.jpg

413 ms

prt_200x200_1712423116.jpg

prt_200x200_1712423116.jpg

433 ms

prt_200x200_1712382321.jpg

prt_200x200_1712382321.jpg

430 ms

prt_200x200_1712532289.jpg

prt_200x200_1712532289.jpg

463 ms

prt_200x200_1712531380.jpg

prt_200x200_1712531380.jpg

462 ms

prt_200x200_1712424214.jpg

prt_200x200_1712424214.jpg

503 ms

prt_200x200_1708711015.jpg

prt_200x200_1708711015.jpg

467 ms

prt_200x200_1712611542.jpg

prt_200x200_1712611542.jpg

475 ms

prt_200x200_1621860664.jpg

prt_200x200_1621860664.jpg

492 ms

prt_200x200_1612365022.png

prt_200x200_1612365022.png

497 ms

prt_200x200_1586234418.png

prt_200x200_1586234418.png

581 ms

prt_200x200_1406310103.jpg

prt_200x200_1406310103.jpg

630 ms

prt_200x200_1570555128.jpg

prt_200x200_1570555128.jpg

523 ms

prt_200x200_1623793903.jpg

prt_200x200_1623793903.jpg

615 ms

prt_200x200_1537370322.png

prt_200x200_1537370322.png

527 ms

prt_200x200_1492549194.png

prt_200x200_1492549194.png

579 ms

prt_200x200_1491773619.png

prt_200x200_1491773619.png

609 ms

prt_200x200_1681595439.png

prt_200x200_1681595439.png

667 ms

analytics.js

analytics.js

86 ms

projects

projects

202 ms

rail.css

rail.css

89 ms

johnbrianking

johnbrianking

80 ms

navigation

navigation

369 ms

johnbrianking

johnbrianking

119 ms

johnbrianking

johnbrianking

188 ms

johnbrianking

johnbrianking

193 ms

johnbrianking

johnbrianking

212 ms

collect

collect

17 ms

collect

collect

18 ms

js

js

58 ms

js

js

79 ms

prt_200x200_1550467627.jpg

prt_200x200_1550467627.jpg

488 ms

prt_200x200_1485269526.jpg

prt_200x200_1485269526.jpg

365 ms

prt_200x200_1485236610.jpg

prt_200x200_1485236610.jpg

384 ms

prt_200x200_1485233999.jpg

prt_200x200_1485233999.jpg

374 ms

prt_200x200_1600366876.jpg

prt_200x200_1600366876.jpg

412 ms

prt_200x200_1452439909.jpg

prt_200x200_1452439909.jpg

392 ms

prt_200x200_1620666248.jpg

prt_200x200_1620666248.jpg

411 ms

prt_200x200_1448206320.jpg

prt_200x200_1448206320.jpg

391 ms

prt_200x200_1485272647.jpg

prt_200x200_1485272647.jpg

427 ms

prt_200x200_1409243426.png

prt_200x200_1409243426.png

463 ms

Accessibility Review

johnbrianking.com accessibility score

52

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

Image elements do not have [alt] attributes

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

johnbrianking.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

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

johnbrianking.com

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