42.2 sec in total
1.4 sec
40.4 sec
409 ms
Welcome to james-watson.com homepage info - get ready to check James Watson best content right away, or after learning these important things about james-watson.com
This is a presentation I've delivered many times and is no less relevant today than five years ago when I first started building successful blogs. The ...
Visit james-watson.comWe analyzed James-watson.com page load time and found that the first response time was 1.4 sec and then it took 40.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
james-watson.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value6.4 s
10/100
25%
Value4.0 s
80/100
10%
Value440 ms
64/100
30%
Value0.003
100/100
15%
Value7.2 s
51/100
10%
1401 ms
2368 ms
2655 ms
2472 ms
2663 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 12% of them (13 requests) were addressed to the original James-watson.com, 38% (40 requests) were made to Static.xx.fbcdn.net and 16% (17 requests) were made to Public.slidesharecdn.com. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain James-watson.com.
Page size can be reduced by 158.8 kB (35%)
453.0 kB
294.2 kB
In fact, the total size of James-watson.com main page is 453.0 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. 70% of websites need less resources to load. Images take 183.1 kB which makes up the majority of the site volume.
Potential reduce by 38.8 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 38.8 kB or 76% of the original size.
Potential reduce by 2.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. James Watson images are well optimized though.
Potential reduce by 32.7 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 32.7 kB or 31% of the original size.
Potential reduce by 84.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. James-watson.com needs all CSS files to be minified and compressed as it can save up to 84.7 kB or 74% of the original size.
Number of requests can be reduced by 59 (65%)
91
32
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of James Watson. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
james-watson.com
1401 ms
style.css
2368 ms
facebook-comments-widgets.css
2655 ms
styles.css
2472 ms
instabuilder.css
2663 ms
colorbox.css
2846 ms
commentluv.css
3467 ms
style.css
5071 ms
jquery.js
5106 ms
jquery-migrate.min.js
5354 ms
core.min.js
5259 ms
jquery.cookie.js
5901 ms
instabuilder.js
6172 ms
w.js
65 ms
analytics.js
15 ms
slideshelf
159 ms
0.jpg
73 ms
count.js
55 ms
collect
24 ms
fan.php
677 ms
123 ms
count-data.js
730 ms
accordion.css
36 ms
tipsy.css
30 ms
2012-sep-obm-content-wordpress-blogs-101-key-121013121218-phpapp01-thumbnail.jpg
234 ms
combined_jquery.js
54 ms
ga.js
22 ms
combined_base.js
51 ms
foaIVY2ZQRgYqC
300 ms
loading.gif
73 ms
__utm.gif
90 ms
__utm.gif
6 ms
combined_jquery.js
100 ms
global.js
130 ms
combined_li_tracking.js
109 ms
font-awesome.css
103 ms
combined_presentation.css
137 ms
combined_player_presentation.js
142 ms
combined_old_embed.js
115 ms
combined_base.js
21 ms
status
79 ms
ga.js
105 ms
beacon.js
125 ms
6-reasons-why-your-wordpress-blog-should-be-your-business-website-1-728.jpg
248 ms
14713683
78 ms
lead-form
110 ms
1x1.gif
56 ms
logo_embed_20x20_v1.png
56 ms
fontawesome-webfont.woff
59 ms
hDvwL1_H7g-.css
111 ms
56WNbrUYLbL.css
133 ms
yZ--Yu0PDbV.css
153 ms
GN27K_co9Wc.css
165 ms
QD6_ejUFoCN.css
183 ms
xxJgcoj8mOR.css
200 ms
IaUW_C3Onoi.css
167 ms
gbh6x73jsGH.css
204 ms
khX_DTDmaMU.css
173 ms
q68gy-v_YMF.js
214 ms
FJmpeSpHpjS.js
228 ms
0wM5s1Khldu.js
213 ms
1bNoFZUdlYZ.js
225 ms
njO1TPvGzoR.js
226 ms
OloiM1PZafe.js
226 ms
LTv6ZK-5zxz.js
257 ms
1FCa-btixu2.js
236 ms
Oagsvfb4VWi.js
238 ms
pObvZSrFc_4.js
238 ms
Kt4tkgSRvHH.js
236 ms
H3EKDTObx05.js
237 ms
eR-qA8bp1RM.js
240 ms
1QuX41zDRrx.js
242 ms
IjqSyiwKeaX.js
253 ms
rBxSIHk4zIe.js
290 ms
n6VgtouijQL.js
289 ms
7BE0CZr3HTs.js
289 ms
pQrUxxo5oQp.js
297 ms
_UYztdBNTjs.js
295 ms
-7JBD_ybv4q.js
299 ms
icons.svg
52 ms
__utm.gif
9 ms
__utm.gif
4 ms
12063368_1019646788087520_8237358855973014879_n.jpg
164 ms
12565618_1075940035791528_8627711136460190761_n.jpg
177 ms
10391747_10209311071712915_4089622635438124927_n.jpg
197 ms
12804859_1337920842888965_6149793788956092662_n.jpg
216 ms
393346_302294929809157_2004160280_n.jpg
236 ms
12803154_10153891058026768_4278345604950236226_n.jpg
344 ms
1010126_10152045696423602_849220108_n.jpg
274 ms
12321410_10206990469054043_5726664092211314964_n.jpg
217 ms
12809514_1668200446779288_8041067393692954772_n.jpg
253 ms
12323545_1665873117012021_726922585_n.jpg
309 ms
12088481_1223287141020003_6016928390868109591_n.jpg
260 ms
8303_10154403824842656_841968362025447399_n.jpg
316 ms
12063368_1019646788087520_8237358855973014879_n.jpg
310 ms
wL6VQj7Ab77.png
91 ms
s7jcwEQH7Sx.png
90 ms
QDwYpIaRyfG.png
92 ms
l5aPruN9xMM.png
91 ms
pimRBh7B6ER.png
90 ms
sSwLTfB7PfP.png
90 ms
K00K-UgnsKu.png
91 ms
b8XhdWI9eAN.js
33 ms
K_65vAc89SX.png
21 ms
I6-MnjEovm5.js
20 ms
rum-track
29 ms
james-watson.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
james-watson.com 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
Page has valid source maps
james-watson.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise James-watson.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 James-watson.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.
james-watson.com
Open Graph data is detected on the main page of James Watson. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: