6.2 sec in total
299 ms
4.6 sec
1.3 sec
Visit johncanning.net now to see the best up-to-date John Canning content and also check out these interesting facts you probably never knew about johncanning.net
Visit johncanning.netWe analyzed Johncanning.net page load time and found that the first response time was 299 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
johncanning.net performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value7.3 s
4/100
25%
Value8.3 s
19/100
10%
Value230 ms
86/100
30%
Value0.014
100/100
15%
Value9.3 s
31/100
10%
299 ms
132 ms
1628 ms
471 ms
252 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 48% of them (41 requests) were addressed to the original Johncanning.net, 15% (13 requests) were made to Pbs.twimg.com and 9% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Johncanning.net.
Page size can be reduced by 618.4 kB (39%)
1.6 MB
970.2 kB
In fact, the total size of Johncanning.net main page is 1.6 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 792.7 kB which makes up the majority of the site volume.
Potential reduce by 103.4 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 103.4 kB or 82% of the original size.
Potential reduce by 41.4 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 Canning images are well optimized though.
Potential reduce by 356.8 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 356.8 kB or 71% of the original size.
Potential reduce by 116.8 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. Johncanning.net needs all CSS files to be minified and compressed as it can save up to 116.8 kB or 70% of the original size.
Number of requests can be reduced by 29 (45%)
65
36
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of John Canning. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
johncanning.net
299 ms
wp
132 ms
1628 ms
wp-emoji-release.min.js
471 ms
frontend_style.css
252 ms
jquery.fancybox-1.3.4.css
302 ms
social_widget.css
219 ms
wpProQuiz_front.min.css
338 ms
css
70 ms
genericons.css
414 ms
style.css
741 ms
stt.min.css
464 ms
default.min.css
430 ms
style.css
466 ms
jquery.js
802 ms
jquery-migrate.min.js
562 ms
jquery.mousewheel-3.0.4.pack.js
593 ms
jquery.fancybox-1.3.4.pack.js
680 ms
frontend_script.js
599 ms
masonry.min.js
691 ms
jquery.masonry.min.js
536 ms
functions.js
575 ms
wp-embed.min.js
690 ms
487 ms
search-icon.png
477 ms
twitter.png
476 ms
twitter.png
475 ms
delicious.png
477 ms
delicious.png
477 ms
digg.png
475 ms
digg.png
621 ms
facebook.png
712 ms
facebook.png
642 ms
technorati.png
710 ms
technorati.png
643 ms
reddit.png
684 ms
reddit.png
777 ms
yahoo.png
863 ms
yahoo.png
772 ms
stumbleupon.png
887 ms
stumbleupon.png
869 ms
53-interesting-ways-to-assess-your-students-192x300.jpg
1148 ms
cover.png
1846 ms
widgets.js
540 ms
JGVZEP92dXgoQBG1CnQcfKCWcynf_cDxXwCLxiixG1c.ttf
442 ms
x-sAbYHwdJCKPJ06aP6Wqw.ttf
476 ms
fpTVHK8qsXbIeTHTrnQH6I48KljrVa8Zcyi9xGGohEU.ttf
492 ms
M2Jd71oPJhLKp0zdtTvoM6xot8ENfkYez2Lz7rcrw70.ttf
495 ms
fpTVHK8qsXbIeTHTrnQH6KQ4IK8jcFikBX2R8jKe4LU.ttf
492 ms
toadOcfmlt9b38dHJxOBGEBls_1aQwi4AfipSOlE3SU.ttf
494 ms
ODelI1aHBYDBqgeIAH2zlFzCdIATDt8zXO3QNtzVeJ8.ttf
534 ms
toadOcfmlt9b38dHJxOBGGAlZ1PukdtTN2z-JxSzbe8.ttf
497 ms
VqvVqv1mv0Gr1Gr9Frul7xuyp+V8XvqnTyb1UoNRm4Af+FsAGNAEuwCFBYsQEBjlmxRgYrWCGwEFlLsBRSWCGwgFkdsAYrXFhZsBQrAAAAAVLP0T8AAA==
8 ms
count.js
487 ms
21a9.png
391 ms
Caffeine.js
5 ms
settings_local.json
33 ms
cbc-videoheartbeat.js
56 ms
caffeine.css
53 ms
Caffeine.modules.js
56 ms
count-data.js
86 ms
vms_5akSXx4Ng_Zn
58 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
119 ms
loading.gif
8 ms
web-sheila-quinn-reads-letter_2500kbps_852x480_2685441528.jpg
67 ms
syndication
82 ms
250219452690481152
164 ms
1f44d-1f3fb.png
32 ms
1f3c9.png
25 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
31 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
68 ms
hhLdVVU1_normal.jpeg
74 ms
wkUM-KBu_normal.jpeg
34 ms
7FgvHgqj_normal.png
31 ms
KIoMAR1L_normal.jpg
32 ms
aWIJn3dH_normal.jpeg
33 ms
kg1FNCjK_normal.jpeg
33 ms
mTNoP-76_normal.jpg
33 ms
7712d34bbfeac2e7a1c89bfb16c6ef15_normal.png
34 ms
JE_portrait_for_Twitter_normal.jpg
33 ms
CdxuoDjXIAAynY7.jpg:small
35 ms
CdGilMdXEAEPOMA.jpg:small
34 ms
CdwO3CuWwAAAYYp.jpg:small
34 ms
CdwO3IaWIAA65YD.jpg:small
35 ms
jot
25 ms
johncanning.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
johncanning.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
johncanning.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johncanning.net 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 Johncanning.net 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.
johncanning.net
Open Graph description is not detected on the main page of John Canning. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: