3.7 sec in total
320 ms
2.6 sec
800 ms
Click here to check amazing Foreverence content for United States. Otherwise, check out these important facts you probably never knew about foreverence.com
Individually designed Foreverence custom urns and memorials are a timeless tribute as unique as the life it represents. Contact us to discuss your design ideas.
Visit foreverence.comWe analyzed Foreverence.com page load time and found that the first response time was 320 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
foreverence.com performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value2.7 s
86/100
25%
Value4.7 s
68/100
10%
Value1,230 ms
19/100
30%
Value0
100/100
15%
Value10.2 s
25/100
10%
320 ms
130 ms
46 ms
50 ms
64 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 91% of them (86 requests) were addressed to the original Foreverence.com, 5% (5 requests) were made to Cdn.shopify.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Cdn.shopify.com.
Page size can be reduced by 233.5 kB (19%)
1.2 MB
988.2 kB
In fact, the total size of Foreverence.com main page is 1.2 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. 70% of websites need less resources to load. Images take 784.3 kB which makes up the majority of the site volume.
Potential reduce by 194.0 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 194.0 kB or 79% of the original size.
Potential reduce by 34.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. Foreverence images are well optimized though.
Potential reduce by 351 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 4.9 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. Foreverence.com has all CSS files already compressed.
Number of requests can be reduced by 57 (61%)
93
36
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foreverence. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
foreverence.com
320 ms
gtm.js
130 ms
vendor-v4.js
46 ms
global.js
50 ms
preloads.js
64 ms
load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js
51 ms
storefront-80e528be853eac23af2454534897ca9536b1d3d04aa043b042f34879a3c111c8.js
53 ms
features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js
54 ms
scripts.js
58 ms
base.css
71 ms
all.min.css
47 ms
globo.formbuilder.index.js
48 ms
shopify-perf-kit-unstable.min.js
66 ms
section-announcement-bar.css
68 ms
announcement-bar.js
110 ms
menu-dropdown.js
112 ms
component-transparent-header.css
114 ms
search-modal.js
117 ms
cart-recommendations.js
117 ms
cart.js
103 ms
cart-drawer.js
104 ms
section-image-banner.css
107 ms
section-video-hero.css
108 ms
component-card.css
109 ms
section-collection-list.css
133 ms
section-rich-text.css
109 ms
section-image-with-text.css
140 ms
section-video.css
134 ms
component-deferred-media.css
132 ms
section-slideshow.css
133 ms
section-logo-list.css
133 ms
section-multicolumn.css
152 ms
section-testimonials.css
147 ms
component-rating.css
149 ms
section-footer.css
158 ms
footer-accordion.js
147 ms
predictive-search.js
198 ms
custom.js
200 ms
trekkie.storefront.72278931d43be9cf54de64f928f82f2eef1fa047.min.js
134 ms
shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js
132 ms
shopify-boomerang-1.0.0.min.js
132 ms
Star.png
46 ms
cross.svg
116 ms
cross.png
270 ms
Logo-colored.png
119 ms
Logo-colored.png
241 ms
Logo-White_2x_bf3494ed-1a83-4864-88ad-d3e93202e6e2.png
270 ms
Logo-White_2x_bf3494ed-1a83-4864-88ad-d3e93202e6e2.png
122 ms
Group_120.jpg
227 ms
Group_122_b8e4b848-6fba-41aa-8fe9-978f1f68bb4c.png
228 ms
Group_216.png
232 ms
Logo-colored.png
240 ms
sezzle-logo.png
1174 ms
1.jpg
320 ms
Custom-Urn-Woody_2.jpg
228 ms
2.jpg
507 ms
3.jpg
366 ms
Untitled-2_5f93644f-5447-4663-ac8e-bcc2d0793ced.jpg
422 ms
b1-mob.jpg
623 ms
b1ssssssssssssssssss.jpg
299 ms
People_Magazine_logo_svg_f8588580-3f06-4d73-98f7-7a4d01f828a3.png
770 ms
58482407cef1014c0b5e49c6_8f08c984-8df7-4303-abd5-5a78df67bbfd.png
661 ms
1200px-TMZLogo_svg.png
661 ms
CBS_logo_svg.png
836 ms
Washington-Times-Logo-02-1024x522-1_5b952123-959a-472e-9898-3e898bc8caa0.png
512 ms
daily-mail-logo-png-transparent_ff938514-2efc-43ee-91d3-eb140641cc48.png
543 ms
ABC_News_logo_2021_svg_1ce9521e-9b65-4caf-ba45-be084bc64def.png
591 ms
1200px-Los_Angeles_Times_logo_svg_389ee1ad-131a-4e78-8b8f-cf2eecd2b75c.png
823 ms
tiktokthumbnail_9dc29989-3130-47e5-84fe-ca6df8574e9c.jpg
640 ms
GalleryFeaturedImage_605a6b0b-b749-477a-8d9a-5329aa275cf0.png
944 ms
placholder-image-testimonials.jpg
691 ms
image_13.jpg
827 ms
image_15.jpg
961 ms
image_17.jpg
986 ms
image_18.jpg
1048 ms
app.js
148 ms
component-predictive-search.css
24 ms
custom.css
30 ms
component-sticky-header.css
39 ms
quattrocentosans_n4.19c4a084d66bf65371b1784dad52aa1acf657cdd.woff
35 ms
component-list-menu.css
22 ms
component-search.css
21 ms
component-menu-drawer.css
20 ms
component-price.css
34 ms
component-loading-overlay.css
32 ms
component-menu-dropdown.css
23 ms
component-cart-recommendations.css
20 ms
component-slider.css
21 ms
component-rte.css
20 ms
component-newsletter.css
21 ms
component-accordion.css
22 ms
component-list-payment.css
24 ms
component-list-social.css
22 ms
disclosure.css
22 ms
script.js
93 ms
foreverence.com accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
foreverence.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
Page has valid source maps
foreverence.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
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 Foreverence.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 Foreverence.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.
foreverence.com
Open Graph data is detected on the main page of Foreverence. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: