23 sec in total
75 ms
22.1 sec
766 ms
Click here to check amazing John Grayson Blog Wordpress content for United States. Otherwise, check out these important facts you probably never knew about johngraysonblog.wordpress.com
- psy-ops by day, fly-by-night | geopolitics in a nutshell | 0xbF3782aD7b0f350614Eb9E685c117425c5e01BDA
Visit johngraysonblog.wordpress.comWe analyzed Johngraysonblog.wordpress.com page load time and found that the first response time was 75 ms and then it took 22.9 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. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
johngraysonblog.wordpress.com performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value19.5 s
0/100
25%
Value3.1 s
93/100
10%
Value7,750 ms
0/100
30%
Value0.529
14/100
15%
Value20.2 s
2/100
10%
75 ms
512 ms
122 ms
365 ms
403 ms
Our browser made a total of 200 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Johngraysonblog.wordpress.com, 11% (22 requests) were made to S.pubmine.com and 10% (20 requests) were made to Usersync.gumgum.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Ssl-market-east.smrtb.com.
Page size can be reduced by 55.8 kB (29%)
191.5 kB
135.7 kB
In fact, the total size of Johngraysonblog.wordpress.com main page is 191.5 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. 40% of websites need less resources to load. Javascripts take 85.9 kB which makes up the majority of the site volume.
Potential reduce by 49.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. 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 49.9 kB or 74% of the original size.
Potential reduce by 35 B
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 Grayson Blog Wordpress images are well optimized though.
Potential reduce by 5.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.
Potential reduce by 282 B
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. Johngraysonblog.wordpress.com has all CSS files already compressed.
Number of requests can be reduced by 143 (79%)
180
37
The browser has sent 180 CSS, Javascripts, AJAX and image requests in order to completely render the main page of John Grayson Blog Wordpress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
johngraysonblog.wordpress.com
75 ms
johngraysonblog.wordpress.com
512 ms
wp-emoji-release.min.js
122 ms
365 ms
403 ms
global.css
331 ms
417 ms
style.css
331 ms
gprofiles.js
388 ms
wpgroho.js
383 ms
322 ms
318 ms
w.js
403 ms
bilmur.min.js
87 ms
globals.css
24 ms
forms.css
11 ms
reveal.css
11 ms
ui.css
61 ms
conf
313 ms
ga.js
308 ms
jupiter.jpg
424 ms
input-bg.png
112 ms
image.jpg
111 ms
formats.png
195 ms
wpcom-gray-white.png
194 ms
untitled.png
664 ms
g.gif
257 ms
hovercard.min.css
115 ms
services.min.css
189 ms
233 ms
g.gif
233 ms
g.gif
233 ms
__utm.gif
55 ms
ata.js
57 ms
5.js
160 ms
pixel
157 ms
tag.js
650 ms
uc.html
647 ms
user_sync.html
638 ms
user_sync.html
668 ms
prbds2s
751 ms
async_usersync.html
723 ms
user_sync.html
602 ms
usync.html
829 ms
checksync.php
881 ms
iframe
604 ms
3.js
255 ms
prebid
987 ms
bidRequest
866 ms
match
158 ms
match
344 ms
30907
1175 ms
setuid
1000 ms
all
19772 ms
match
839 ms
sync
593 ms
PugMaster
1287 ms
jslog
324 ms
URnmbSKM
1974 ms
user_sync.html
420 ms
sync
398 ms
match
392 ms
match
586 ms
1551 ms
0.gif
1671 ms
usync.js
449 ms
pd
579 ms
match
856 ms
1774 ms
usersync.aspx
2128 ms
pixel
1773 ms
usermatch
784 ms
match
702 ms
match
698 ms
cksync.php
2347 ms
match
661 ms
match
1047 ms
cksync.php
2316 ms
match
1046 ms
engine
3012 ms
862f2066-9598-e222-db36-967e44e5bcd1
2150 ms
ny75r2x0
2877 ms
ix
2550 ms
blank.html
3277 ms
match
1190 ms
us.gif
975 ms
match
963 ms
match
1305 ms
us.gif
1881 ms
cksync.php
2809 ms
us.gif
1934 ms
us.gif
1741 ms
us.gif
3650 ms
demconf.jpg
1176 ms
us.gif
2510 ms
us.gif
2497 ms
usersync
3642 ms
b9pj45k4
2471 ms
match
1137 ms
5E961CA6-1B0B-41C3-A822-BC93BD21DA00
2446 ms
pixel
2472 ms
pixel
2378 ms
usersync
3152 ms
cksync.php
3777 ms
usync.html
1258 ms
usync.html
2432 ms
usersync
3041 ms
usersync
3077 ms
cksync.html
3079 ms
usersync
3056 ms
usersync
3691 ms
pixel
2122 ms
usersync
3813 ms
info2
1836 ms
pixel
2048 ms
usersync
3716 ms
pixel
2235 ms
openx
1580 ms
us.gif
3437 ms
1000.gif
1732 ms
Pug
3433 ms
usg.gif
3299 ms
user_sync.html
1477 ms
us.gif
3027 ms
rtset
1233 ms
usersync
2877 ms
match
1461 ms
match
1443 ms
usersync
2834 ms
usync.html
1386 ms
tap.php
1798 ms
PugMaster
1194 ms
PugMaster
1480 ms
Pug
2532 ms
Pug
2499 ms
cksync
1670 ms
PugMaster
1546 ms
usersync
2195 ms
Pug
2364 ms
cksync.php
2132 ms
usersync
2347 ms
usersync
2435 ms
sd
919 ms
usersync
2263 ms
dcm
949 ms
rum
2379 ms
tap.php
1473 ms
usermatchredir
1108 ms
cksync
1427 ms
sd
1008 ms
match
708 ms
pixel
1015 ms
dcm
993 ms
pixel
993 ms
sd
869 ms
cksync.php
1069 ms
match
1884 ms
cksync.php
1071 ms
cksync.php
1868 ms
usersync
1696 ms
info
1048 ms
g.pixel
1859 ms
usersync.aspx
1040 ms
Pug
1736 ms
usersync
1624 ms
match
1020 ms
match
1541 ms
tap.php
1212 ms
crum
1519 ms
1151 ms
Pug
1271 ms
match
899 ms
match
908 ms
sync
904 ms
usersync
942 ms
Pug
970 ms
crum
887 ms
Pug
807 ms
Pug
807 ms
match
542 ms
cksync.php
543 ms
usersync
340 ms
Pug
262 ms
ecm3
254 ms
ecm3
281 ms
cs&eq_cc=1
197 ms
cksync.php
382 ms
match
198 ms
Pug
117 ms
crum
105 ms
match
87 ms
crum
54 ms
usersync
55 ms
usersync
75 ms
Pug
73 ms
Artemis
108 ms
match
58 ms
Pug
54 ms
match
9 ms
725X1342.skimlinks.js
55 ms
johngraysonblog.wordpress.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.
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
Image elements do not have [alt] attributes
johngraysonblog.wordpress.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
Browser errors were logged to the console
johngraysonblog.wordpress.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johngraysonblog.wordpress.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 Johngraysonblog.wordpress.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.
johngraysonblog.wordpress.com
Open Graph data is detected on the main page of John Grayson Blog Wordpress. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: