6 sec in total
431 ms
5.2 sec
429 ms
Click here to check amazing William Holsinger content. Otherwise, check out these important facts you probably never knew about williamholsinger.com
Will Holsinger is a certified hospice volunteer who wrote a collection of insightful and compassionate poems, musings and insights about death and dying.
Visit williamholsinger.comWe analyzed Williamholsinger.com page load time and found that the first response time was 431 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
williamholsinger.com performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value16.7 s
0/100
25%
Value15.3 s
1/100
10%
Value1,550 ms
13/100
30%
Value0.099
90/100
15%
Value16.0 s
6/100
10%
431 ms
31 ms
53 ms
196 ms
269 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 24% of them (19 requests) were addressed to the original Williamholsinger.com, 60% (48 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (767 ms) belongs to the original domain Williamholsinger.com.
Page size can be reduced by 529.9 kB (15%)
3.4 MB
2.9 MB
In fact, the total size of Williamholsinger.com main page is 3.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 120.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 120.4 kB or 77% of the original size.
Potential reduce by 384.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. Obviously, William Holsinger needs image optimization as it can save up to 384.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 12.0 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 12.0 kB or 18% of the original size.
Potential reduce by 13.2 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. Williamholsinger.com needs all CSS files to be minified and compressed as it can save up to 13.2 kB or 24% of the original size.
Number of requests can be reduced by 10 (34%)
29
19
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of William Holsinger. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.williamholsinger.com
431 ms
a76jg.css
31 ms
js
53 ms
all.css
196 ms
fqybt.js
269 ms
api.js
49 ms
addthis_widget.js
40 ms
autoptimize_6c7e49b3df7df8cbe922fa510dd923c5.js
29 ms
analytics.js
43 ms
collect
12 ms
recaptcha__en.js
219 ms
logo.png
191 ms
A-Life-Well-Lived-Cover-CS-9-12-2018.png
278 ms
1.-Sunsetphoto_edited.jpg
635 ms
Rock-in-Ocean-300x225.jpg
314 ms
12b.-Graeagle-Falls-color-photo.jpeg
600 ms
A-Life-Well-Lived-3D-3600.png
313 ms
Three-Seated-Men-bw-sketch.jpg
307 ms
08.-Two-Seated-men-Both-Wearing-Hats-bw-sketch.jpg
767 ms
09.-Man-Looking-Down-bw-sketch.jpg
355 ms
amazon-logo_black.png
358 ms
bn-icon-192x192.jpg
349 ms
amazon_kindle.png
369 ms
store_logos_07-150x114.png
374 ms
S6uyw4BMUTPHjxAwWA.woff
199 ms
S6uyw4BMUTPHjxAwWw.ttf
215 ms
S6u9w4BMUTPHh7USSwaPHw.woff
236 ms
S6u9w4BMUTPHh7USSwaPHA.ttf
234 ms
S6u8w4BMUTPHh30AUi-s.woff
234 ms
S6u8w4BMUTPHh30AUi-v.ttf
236 ms
S6u9w4BMUTPHh6UVSwaPHw.woff
262 ms
S6u9w4BMUTPHh6UVSwaPHA.ttf
260 ms
S6u9w4BMUTPHh50XSwaPHw.woff
260 ms
S6u9w4BMUTPHh50XSwaPHA.ttf
259 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aHUlM.woff
258 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aHUlP.ttf
263 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDeJ2aHUlM.woff
265 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDeJ2aHUlP.ttf
265 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDJp2aHUlM.woff
263 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDJp2aHUlP.ttf
265 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDypqaHUlM.woff
266 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDypqaHUlP.ttf
268 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaHUlM.woff
270 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaHUlP.ttf
273 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDppqaHUlM.woff
270 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDppqaHUlP.ttf
271 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDeJqaHUlM.woff
271 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDeJqaHUlP.ttf
272 ms
co3YmX5slCNuHLi8bLeY9MK7whWMhyjQWlhfsA-O.woff
273 ms
co3YmX5slCNuHLi8bLeY9MK7whWMhyjQWlhfsA-N.ttf
279 ms
co3bmX5slCNuHLi8bLeY9MK7whWMhyjYp3tM.woff
276 ms
co3bmX5slCNuHLi8bLeY9MK7whWMhyjYp3tP.ttf
276 ms
co3YmX5slCNuHLi8bLeY9MK7whWMhyjQAllfsA-O.woff
277 ms
co3YmX5slCNuHLi8bLeY9MK7whWMhyjQAllfsA-N.ttf
276 ms
co3YmX5slCNuHLi8bLeY9MK7whWMhyjQdl9fsA-O.woff
275 ms
co3YmX5slCNuHLi8bLeY9MK7whWMhyjQdl9fsA-N.ttf
281 ms
co3YmX5slCNuHLi8bLeY9MK7whWMhyjQEl5fsA-O.woff
281 ms
co3YmX5slCNuHLi8bLeY9MK7whWMhyjQEl5fsA-N.ttf
283 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNlwV3lGb7U.woff
281 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNlwV3lGb7Y.ttf
280 ms
modules.ttf
396 ms
moatframe.js
197 ms
fa-brands-400.woff
155 ms
_ate.track.config_resp
331 ms
300lo.json
272 ms
sh.f48a1a04fe8dbf021b4cda1d.html
77 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNlCV3lGb7U.woff
82 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNlCV3lGb7Y.ttf
71 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNkcV3lGb7U.woff
56 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNkcV3lGb7Y.ttf
57 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNnCV3lGb7U.woff
56 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNnCV3lGb7Y.ttf
101 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNmcUHlGb7U.woff
100 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNmcUHlGb7Y.ttf
100 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNmlUHlGb7U.woff
100 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNmlUHlGb7Y.ttf
100 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNnCUHlGb7U.woff
100 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNnCUHlGb7Y.ttf
99 ms
layers.fa6cd1947ce26e890d3d.js
10 ms
hip0.css
12 ms
williamholsinger.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
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
Links do not have a discernible name
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
williamholsinger.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
williamholsinger.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Williamholsinger.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 Williamholsinger.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.
williamholsinger.com
Open Graph data is detected on the main page of William Holsinger. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: