5.8 sec in total
527 ms
4.5 sec
722 ms
Welcome to sayinggoodbye.org homepage info - get ready to check Saying Goodbye best content right away, or after learning these important things about sayinggoodbye.org
#description
Visit sayinggoodbye.orgWe analyzed Sayinggoodbye.org page load time and found that the first response time was 527 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
sayinggoodbye.org performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value8.7 s
1/100
25%
Value11.6 s
4/100
10%
Value3,880 ms
1/100
30%
Value0.001
100/100
15%
Value12.1 s
16/100
10%
527 ms
52 ms
279 ms
50 ms
384 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 54% of them (22 requests) were addressed to the original Sayinggoodbye.org, 17% (7 requests) were made to Fonts.gstatic.com and 7% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (770 ms) relates to the external source App.mailerlite.com.
Page size can be reduced by 119.5 kB (15%)
793.4 kB
673.9 kB
In fact, the total size of Sayinggoodbye.org main page is 793.4 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. 80% 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 476.5 kB which makes up the majority of the site volume.
Potential reduce by 119.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 119.4 kB or 86% 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. Saying Goodbye images are well optimized though.
Potential reduce by 89 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 0 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. Sayinggoodbye.org has all CSS files already compressed.
Number of requests can be reduced by 12 (36%)
33
21
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Saying Goodbye. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.sayinggoodbye.org
527 ms
webfontloader.min.js
52 ms
b216088006aadc1ea1cf7bafaf9f1db2.css
279 ms
jquery.min.js
50 ms
email-decode.min.js
384 ms
u5r3g2.js
770 ms
eb89d6f7a8923206d7d2dd6fa01a196e.js
382 ms
css
353 ms
sg-logo.png
297 ms
365003058
434 ms
symbol-defs.svg
244 ms
sg-icon-pink-crop-vsml.png
232 ms
sg-leafletheart-1024x923.jpg
232 ms
mariposa-trust.jpg
234 ms
Kate-Ferdinand.jpg
581 ms
sg-book.jpg
266 ms
baby-loss-guide-cover-638x1024-1.jpg
262 ms
beyond-goodbye-cover-637x1024-1.jpg
681 ms
pregnancy-after-loss-cover.jpg
258 ms
life-soul.jpg
254 ms
about-image-2-325x130.jpg
572 ms
andyandzoe-banner-325x130.jpg
271 ms
thankyou-banner-325x130.jpg
270 ms
mariposa-store.jpg
293 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
79 ms
S6uyw4BMUTPHjx4wWw.ttf
196 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
196 ms
tDbD2oWUg0MKqScQ6A.ttf
197 ms
S6u_w4BMUTPHjxsI9w2_Gwfo.ttf
227 ms
S6u8w4BMUTPHjxsAXC-v.ttf
231 ms
S6u_w4BMUTPHjxsI5wq_Gwfo.ttf
353 ms
css
138 ms
css
175 ms
rolling@2x.gif
338 ms
webforms.min.js
379 ms
820874836-593d61aaa783accc8ca82be402d1a3fc5582d633c1b99dc12885ce18dee6c6dc-d.jpg
276 ms
player.js
344 ms
player.css
274 ms
picturefill.min.js
113 ms
ml_jQuery.inputmask.bundle.min.js
244 ms
820874836-593d61aaa783accc8ca82be402d1a3fc5582d633c1b99dc12885ce18dee6c6dc-d
56 ms
sayinggoodbye.org accessibility score
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
Form elements do not have associated labels
sayinggoodbye.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
sayinggoodbye.org SEO score
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 Sayinggoodbye.org 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 Sayinggoodbye.org 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.
sayinggoodbye.org
Open Graph data is detected on the main page of Saying Goodbye. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: