8 sec in total
3.1 sec
4.4 sec
530 ms
Click here to check amazing Coming Alive content. Otherwise, check out these important facts you probably never knew about comingalive.ca
Nutritionist, holistic nutrition, weight loss, pain management, disorders, diabetes, addictions, ADD, depression support for Sarnia and Lambton County.
Visit comingalive.caWe analyzed Comingalive.ca page load time and found that the first response time was 3.1 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
comingalive.ca performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value19.4 s
0/100
25%
Value16.0 s
0/100
10%
Value580 ms
51/100
30%
Value0.018
100/100
15%
Value17.9 s
4/100
10%
3114 ms
247 ms
42 ms
35 ms
266 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 65% of them (55 requests) were addressed to the original Comingalive.ca, 31% (26 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Comingalive.ca.
Page size can be reduced by 582.1 kB (15%)
4.0 MB
3.4 MB
In fact, the total size of Comingalive.ca main page is 4.0 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.3 MB which makes up the majority of the site volume.
Potential reduce by 89.6 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. This page needs HTML code to be minified as it can gain 11.5 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 89.6 kB or 82% of the original size.
Potential reduce by 347.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, Coming Alive needs image optimization as it can save up to 347.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 83.9 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 83.9 kB or 21% of the original size.
Potential reduce by 61.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. Comingalive.ca needs all CSS files to be minified and compressed as it can save up to 61.2 kB or 39% of the original size.
Number of requests can be reduced by 46 (81%)
57
11
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Coming Alive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
comingalive.ca
3114 ms
utilities.css
247 ms
style.css
42 ms
css
35 ms
elementor-icons.min.css
266 ms
frontend-lite.min.css
333 ms
swiper.min.css
267 ms
post-5.css
343 ms
frontend-lite.min.css
62 ms
global.css
63 ms
post-230.css
70 ms
post-3145.css
83 ms
post-3139.css
95 ms
post-3103.css
107 ms
post-3132.css
116 ms
post-298.css
128 ms
style.css
140 ms
css
33 ms
fontawesome.min.css
150 ms
brands.min.css
160 ms
utilities.js
179 ms
jquery.min.js
193 ms
jquery-migrate.min.js
207 ms
email-decode.min.js
208 ms
widget-icon-list.min.css
218 ms
css
33 ms
rs6.css
237 ms
rbtools.min.js
249 ms
rs6.min.js
257 ms
underscore.min.js
262 ms
wp-util.min.js
271 ms
main.js
565 ms
nav-mobile.js
269 ms
webpack.runtime.min.js
271 ms
frontend-modules.min.js
566 ms
waypoints.min.js
279 ms
core.min.js
287 ms
frontend.min.js
290 ms
testimonial.js
303 ms
slick.min.js
300 ms
webpack-pro.runtime.min.js
265 ms
wp-polyfill-inert.min.js
260 ms
regenerator-runtime.min.js
276 ms
wp-polyfill.min.js
270 ms
hooks.min.js
518 ms
i18n.min.js
320 ms
frontend.min.js
308 ms
elements-handlers.min.js
498 ms
elementor.js
287 ms
comingalive-logo-vertical-300x235.png
301 ms
comingalive-logo-vertical.png
41 ms
dummy.png
41 ms
sarnia-nutritionist-slider-1.png
72 ms
vegetables3b-1024x1008.jpg
222 ms
eat_real-_food.png
852 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff
180 ms
font
179 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrc.woff
179 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrc.woff
178 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff
179 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrc.woff
184 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrc.woff
181 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff
183 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff
181 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrc.woff
180 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrc.woff
182 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrc.woff
186 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff
182 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff
185 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff
182 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff
184 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXw.woff
183 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXw.woff
185 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff
185 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff
186 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
185 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff
186 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff
186 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXw.woff
187 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff
187 ms
vegetables2-pixabay.jpg
775 ms
fruit-pixabay-1.jpg
162 ms
fa-brands-400.woff
523 ms
pxiByp8kv8JHgFVrLCz7Z1xlEw.woff
90 ms
comingalive.ca 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.
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
comingalive.ca 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
comingalive.ca 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 Comingalive.ca 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 Comingalive.ca 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.
comingalive.ca
Open Graph data is detected on the main page of Coming Alive. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: