2.9 sec in total
83 ms
2.5 sec
402 ms
Visit johnathanlaird.com now to see the best up-to-date Johnathanlaird content and also check out these interesting facts you probably never knew about johnathanlaird.com
A professional blog about pharmacy...by pharmacists...mostly!
Visit johnathanlaird.comWe analyzed Johnathanlaird.com page load time and found that the first response time was 83 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
johnathanlaird.com performance score
83 ms
590 ms
155 ms
229 ms
228 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Johnathanlaird.com, 47% (53 requests) were made to Johnathanlaird.files.wordpress.com and 8% (9 requests) were made to S2.wp.com. The less responsive or slowest element that took the longest time to load (999 ms) relates to the external source Johnathanlaird.files.wordpress.com.
Page size can be reduced by 573.2 kB (2%)
24.9 MB
24.3 MB
In fact, the total size of Johnathanlaird.com main page is 24.9 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. Only a small number of websites need less resources to load. Images take 24.1 MB which makes up the majority of the site volume.
Potential reduce by 101.5 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 101.5 kB or 80% of the original size.
Potential reduce by 4.5 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. Johnathanlaird images are well optimized though.
Potential reduce by 454.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 454.8 kB or 67% of the original size.
Potential reduce by 12.5 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. Johnathanlaird.com needs all CSS files to be minified and compressed as it can save up to 12.5 kB or 69% of the original size.
Number of requests can be reduced by 31 (31%)
100
69
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Johnathanlaird. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
johnathanlaird.com
83 ms
johnathanlaird.com
590 ms
webfont.js
155 ms
229 ms
228 ms
style.css
208 ms
gprofiles.js
398 ms
wpgroho.js
189 ms
209 ms
187 ms
tiled-gallery.css
235 ms
238 ms
widgets.js
244 ms
186 ms
w.js
236 ms
css
125 ms
cru1our.js
428 ms
merriweather.css
26 ms
cropped-cropped-img_0656.jpg
416 ms
bg-trends.png
506 ms
beacon-archive-trending.png
69 ms
2c94c078697b91fca6647fb7d0d1140f
722 ms
421f2ab02d36cf2b535dcc419d9b0a5f
720 ms
b556dd0b552bda921ab48b8abfcffff0
799 ms
icon-trends.png
69 ms
60d6e0a3562798c55bc50b31dfdbe179
151 ms
c64a971c92cbe82789a0df0598d780b3
384 ms
ddddddd.jpg
399 ms
tech.jpg
398 ms
hayley.png
399 ms
alistair.jpg
399 ms
john-sargeant-jpeg.jpg
490 ms
vikkiharris-author-pic.jpg
489 ms
calum.jpg
491 ms
moh.png
560 ms
hadar.jpg
489 ms
hala.png
562 ms
img_0671.jpg
566 ms
grundy.jpg
567 ms
wp-1453663507232.jpeg
698 ms
shaun.jpg
565 ms
charles-willis.png
698 ms
imag0903.jpg
778 ms
img_0694.png
999 ms
Genericons.svg
24 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
21 ms
u8HSyiSSzbmPRVNA5BNhqA.woff
423 ms
2yXG0u2oPiXdRt7OARC1e_esZW2xOQ-xsNqO47m55DA.woff
670 ms
F3_q9tzkRUEMjTtsySoCaA.woff
737 ms
cxbOUSTgtyl7V_qnBf4BYxsxEYwM7FgeyaSgU71cLG0.woff
741 ms
platform.js
508 ms
ga.js
447 ms
Noticons.svg
343 ms
BaABdRAi2AAAA
70 ms
merriweather-bold-webfont.ttf
208 ms
merriweather-regular-webfont.ttf
273 ms
merriweather-light-webfont.ttf
207 ms
hovercard.css
298 ms
services.css
455 ms
slideshow-loader.gif
138 ms
img_0571-0.jpg
499 ms
wpid-imag0489.jpg
712 ms
wp-1448666568640.png
510 ms
imag0903.jpg
790 ms
img_0602.jpg
506 ms
img_04411.jpg
502 ms
wpid-imag0653.jpg
512 ms
wpid-wp-1443715510775.jpeg
705 ms
wpid-wp-1444938732146.jpeg
791 ms
wpid-wp-1448361586487.jpeg
708 ms
img_0255.jpg
715 ms
wpid-imag0603.jpg
784 ms
img_0325-0.jpg
720 ms
img_0622.jpg
712 ms
imag0802.jpg
856 ms
wpid-imag0533.jpg
793 ms
img_0612.jpg
780 ms
imag0806.jpg
874 ms
d
252 ms
g.gif
469 ms
g.gif
434 ms
g.gif
436 ms
imag0839.jpg
749 ms
wp-1448666551902.png
792 ms
img_0666.png
743 ms
wpid-imag0536.jpg
753 ms
imag0813.jpg
746 ms
img_0125-0.jpg
666 ms
imag0808.jpg
707 ms
img_0655.jpg
663 ms
img_0126-0.jpg
667 ms
americans.png
603 ms
img_0607.jpg
603 ms
image1.jpeg
605 ms
img_0613.jpg
602 ms
index.html
125 ms
__utm.gif
96 ms
wpid-imag0651.jpg
494 ms
img_0145.jpg
490 ms
img_0343.jpg
489 ms
jquery.js
215 ms
img_0642.jpg
410 ms
collect
283 ms
HT+w8D4rzvP75+EySOz6TmpuRlFxQW5ZeWUVJVXfn81RsdvI4X+C9dV51J
187 ms
slideshow-controls.png
198 ms
p.gif
124 ms
postmessage.js
15 ms
jed.js
15 ms
underscore.min.js
15 ms
jquery.wpcom-proxy-request.js
3 ms
40 ms
7 ms
follow-rest.js
3 ms
johnathanlaird.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johnathanlaird.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 Johnathanlaird.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.
johnathanlaird.com
Open Graph data is detected on the main page of Johnathanlaird. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: