1.3 sec in total
13 ms
782 ms
500 ms
Click here to check amazing Thomas Fh content. Otherwise, check out these important facts you probably never knew about thomasfh.com
Thomas Funeral Homes in Centerville, Corydon, Moulton, and Seymour, IA provides funeral, memorial, aftercare, pre-planning, and cremation services to our community and the surrounding areas.
Visit thomasfh.comWe analyzed Thomasfh.com page load time and found that the first response time was 13 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
thomasfh.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value6.8 s
7/100
25%
Value5.7 s
51/100
10%
Value340 ms
74/100
30%
Value0.07
96/100
15%
Value12.3 s
15/100
10%
13 ms
28 ms
72 ms
66 ms
81 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 24% of them (11 requests) were addressed to the original Thomasfh.com, 35% (16 requests) were made to D2zeeo94hsmapq.cloudfront.net and 13% (6 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (496 ms) relates to the external source Tributecenteronline.s3-accelerate.amazonaws.com.
Page size can be reduced by 357.9 kB (8%)
4.3 MB
4.0 MB
In fact, the total size of Thomasfh.com main page is 4.3 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.9 MB which makes up the majority of the site volume.
Potential reduce by 150.5 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 150.5 kB or 73% of the original size.
Potential reduce by 204.3 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. Thomas Fh images are well optimized though.
Potential reduce by 74 B
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 3.0 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. Thomasfh.com has all CSS files already compressed.
Number of requests can be reduced by 24 (57%)
42
18
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thomas Fh. 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 from 15 to 1 for CSS and as a result speed up the page load time.
thomasfh.com
13 ms
www.thomasfh.com
28 ms
www.thomasfh.com
72 ms
gtm.js
66 ms
gtm.js
81 ms
common.css
22 ms
tribute-pay-panel.css
24 ms
lightbox.css
26 ms
2ea18e93d7b4278a63e09a302acc095a.513.css
12 ms
rotating-banner.css
29 ms
8577586dc142bd1cbb54c69235ec0888.513.css
30 ms
obituaries-homepage.css
26 ms
feeefa511254c061e8ad7d0fbd7de833.513.css
34 ms
shared.css
26 ms
fonts.css
28 ms
0c28e5df75513ba69612ad23749e7fe0.513.css
38 ms
DynamicForms.css
28 ms
679da333f9a713965154d43db16f6c39.513.css
32 ms
aos.css
30 ms
client.js
42 ms
a8a3e82cac3d843eada747ccf2fe5c89.513.js
43 ms
aos.js
32 ms
site.css
113 ms
js
75 ms
js
102 ms
thomasfhlogo_92e351b59f214ed5818a1a263d57911e.png
86 ms
41a51b0f-d2da-4418-aed5-ab1a00aec701.jpg
297 ms
thomasfhlogo_92e351b59f214ed5818a1a263d57911e.png
139 ms
a5381c0b-5f5d-4f96-9792-86f9ae133c6e.jpg
227 ms
b6953f9a-b268-4755-a986-8c29439c8ba3.jpg
227 ms
21c2f8ea-1291-4e2a-a0d7-34cf272ff3fb.jpg
228 ms
bf06ec5f-8d1a-440d-b11f-fa9589595127.jpg
272 ms
d0a72b5c-0493-4cd5-bacd-f5ebe4c74cac.jpg
496 ms
Arrows_Left.svg
115 ms
Arrows_Right.svg
225 ms
chooseus.jpg
292 ms
flowers.jpg
69 ms
email.jpg
226 ms
js
83 ms
analytics.js
201 ms
js
64 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_GbQbMZhKg.ttf
169 ms
web-vitals.umd.js
76 ms
collect
37 ms
collect
34 ms
collect
17 ms
thomasfh.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
thomasfh.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
thomasfh.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
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thomasfh.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Thomasfh.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.
thomasfh.com
Open Graph description is not detected on the main page of Thomas Fh. 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: