1.1 sec in total
34 ms
836 ms
218 ms
Welcome to peterhgregory.com homepage info - get ready to check Peter H Gregory best content right away, or after learning these important things about peterhgregory.com
Updated August 10, 2023 I was fortunate to be "pulled in" to the tech book publishing industry, when a colleague asked me to participate in writing her book on database performance tuning. That projec...
Visit peterhgregory.comWe analyzed Peterhgregory.com page load time and found that the first response time was 34 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
peterhgregory.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value4.9 s
29/100
25%
Value4.8 s
67/100
10%
Value1,020 ms
26/100
30%
Value0
100/100
15%
Value16.6 s
5/100
10%
34 ms
6 ms
21 ms
88 ms
94 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Peterhgregory.com, 20% (13 requests) were made to D3iqo9kw2lsf1n.cloudfront.net and 11% (7 requests) were made to S2.wp.com. The less responsive or slowest element that took the longest time to load (343 ms) relates to the external source C20.statcounter.com.
Page size can be reduced by 117.9 kB (13%)
898.9 kB
781.0 kB
In fact, the total size of Peterhgregory.com main page is 898.9 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. 65% of websites need less resources to load. Images take 451.8 kB which makes up the majority of the site volume.
Potential reduce by 88.6 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 88.6 kB or 74% of the original size.
Potential reduce by 26.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. Peter H Gregory images are well optimized though.
Potential reduce by 2.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 307 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. Peterhgregory.com has all CSS files already compressed.
Number of requests can be reduced by 36 (65%)
55
19
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Peter H Gregory. 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 13 to 1 for CSS and as a result speed up the page load time.
peterhgregory.com
34 ms
peterhgregory.wordpress.com
6 ms
peterhgregory.wordpress.com
21 ms
88 ms
94 ms
100 ms
102 ms
106 ms
verbum-comments.css
109 ms
block-editor.css
113 ms
css
130 ms
99 ms
108 ms
106 ms
119 ms
hovercards.min.js
106 ms
wpgroho.js
108 ms
106 ms
w.js
118 ms
webfont.js
56 ms
conf
319 ms
ga.js
236 ms
card
263 ms
b78a4a61db21a8428ad4949db64d65c6da8046006092b65dcfdc5bc889ce1dc2
81 ms
0082156a4e9e3c3f462cf8a09651c350e5a7135b46a7b34b53eac1ac6645eb69
37 ms
amazon-black.jpeg
254 ms
44a044d8a26da257ba78e5a3bab203528fdd502cd696055147b98a4cc6efacdd
331 ms
master.html
27 ms
wpcom-mark.svg
25 ms
g.gif
236 ms
241 ms
g.gif
226 ms
g.gif
233 ms
6549abf87f82291f82ba4993fe18ac169b2695591c1157525c89a329990c249e
40 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
233 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
233 ms
nib2yyi.js
337 ms
rlt-proxy.js
195 ms
195 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf
81 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf
82 ms
__utm.gif
64 ms
counter.php
343 ms
kp.kcard.css
75 ms
kcard.min.js
100 ms
amazon-black.jpeg
104 ms
ata.js
71 ms
ATVPDKIKX0DER:000-1312701-2290960:JND7AEERF17QCE510FB7$uedata=s:https%3A%2F%2Fread.amazon.com%2Fkp%2Fuedata%2Fuedata%3Fstaticb%26id%3DJND7AEERF17QCE510FB7:0
113 ms
51hQLvHVuyL._SL500_.jpg
243 ms
uploadMetrics
154 ms
cxguardrails_config_prod._TTH_.js
224 ms
embed
78 ms
d
149 ms
d
150 ms
p.gif
169 ms
kp.desktop.css
60 ms
require.js
63 ms
jquery.js
65 ms
KPUtils.min.js
65 ms
kp.min.js
65 ms
Chrome.png
17 ms
Firefox.png
18 ms
Safari.png
17 ms
IE.png
18 ms
q.js
24 ms
WishListView.js
39 ms
peterhgregory.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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
peterhgregory.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
Issues were logged in the Issues panel in Chrome Devtools
peterhgregory.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
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 Peterhgregory.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 Peterhgregory.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.
peterhgregory.com
Open Graph data is detected on the main page of Peter H Gregory. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: