4 sec in total
61 ms
3.1 sec
847 ms
Click here to check amazing Preston Hanley content for United States. Otherwise, check out these important facts you probably never knew about preston-hanley.com
See all locations in the Preston-Hanley family. View obituaries and services, get directions and get in touch 24/7.
Visit preston-hanley.comWe analyzed Preston-hanley.com page load time and found that the first response time was 61 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
preston-hanley.com performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value6.8 s
7/100
25%
Value19.5 s
0/100
10%
Value25,920 ms
0/100
30%
Value0.001
100/100
15%
Value39.1 s
0/100
10%
61 ms
89 ms
431 ms
87 ms
77 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Preston-hanley.com, 26% (22 requests) were made to Cdn.dignitymemorial.com and 14% (12 requests) were made to Dignitymemorial.com. The less responsive or slowest element that took the longest time to load (774 ms) relates to the external source Ampcid.google.com.
Page size can be reduced by 82.1 kB (16%)
506.3 kB
424.2 kB
In fact, the total size of Preston-hanley.com main page is 506.3 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. Javascripts take 180.7 kB which makes up the majority of the site volume.
Potential reduce by 74.3 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 74.3 kB or 72% of the original size.
Potential reduce by 0 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. Preston Hanley images are well optimized though.
Potential reduce by 7.6 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 221 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. Preston-hanley.com has all CSS files already compressed.
Number of requests can be reduced by 48 (64%)
75
27
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Preston Hanley. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and as a result speed up the page load time.
preston-hanley.com
61 ms
www.preston-hanley.com
89 ms
preston-hanley
431 ms
optimize.js
87 ms
8298c6bc3c0e43bf8ed959f185e3e2a0.js.ubembed.com
77 ms
vendor.min.css
208 ms
dm3-core.min.css
287 ms
dm3-group.min.css
343 ms
VisitorIdentification.js
49 ms
vendor.js
410 ms
DignityMemorial.Foundation.Search.Utils.js
167 ms
DignityMemorial.Feature.Forms.js
170 ms
js
51 ms
recentobituaries
337 ms
dm3-core.min.js
382 ms
handlebars.min-v4.7.7.js
383 ms
require.min.js
383 ms
lazy-initializer.min.js
381 ms
dm3-group.min.js
381 ms
bundle.js
56 ms
gtm.js
249 ms
dm3-icons.png
80 ms
star.svg
87 ms
Lato-Regular.woff
88 ms
Lato-Bold.woff
92 ms
star-e.svg
90 ms
star-75.svg
88 ms
map-view-icon.svg
109 ms
analytics.js
258 ms
conversion_async.js
321 ms
web-vitals.iife.js
319 ms
fbevents.js
308 ms
up_loader.1.1.0.js
611 ms
631 ms
ping.min.js
630 ms
js
294 ms
list-view-icon.svg
247 ms
map-view-icon-white.svg
250 ms
list-view-icon-white.svg
247 ms
MrsEavesOT-Roman.woff
250 ms
MrsEaves-Italic.woff
216 ms
dm3-icons.png
373 ms
publisher:getClientId
774 ms
web-vitals.iife.js
461 ms
694 ms
1860237160926887
197 ms
conversion
493 ms
gen_204
331 ms
intersection-observer-amd.min.js
259 ms
lazyload.amd.min.js
328 ms
343 ms
328 ms
334 ms
state-dropdown.json
272 ms
RecentObituariesComponent
289 ms
115 ms
collect
52 ms
collect
38 ms
52 ms
d9core
103 ms
57 ms
47 ms
ga-audiences
44 ms
invoca-latest.min.js
81 ms
38799-source
57 ms
pixel
79 ms
relocation-protection-icon.svg
68 ms
lifetime-flexibility-icon.svg
66 ms
lgc
83 ms
lgc
104 ms
26 ms
15 ms
img.png
125 ms
getuid
41 ms
13 ms
nr-spa-1216.min.js
77 ms
pd.js
95 ms
up
17 ms
up
40 ms
universal_pixel.1.1.0.js
49 ms
eac7771f5a
168 ms
analytics
243 ms
rubicon
17 ms
rum
31 ms
generic
18 ms
preston-hanley.com accessibility score
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
Links do not have a discernible name
preston-hanley.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
Page has valid source maps
preston-hanley.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
Image elements do not have [alt] attributes
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
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 Preston-hanley.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 Preston-hanley.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.
preston-hanley.com
Open Graph description is not detected on the main page of Preston Hanley. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: