3.2 sec in total
174 ms
2 sec
1.1 sec
Click here to check amazing Caneelian content. Otherwise, check out these important facts you probably never knew about caneelian.com
After three fails in one week, I'm realizing the commitment problem has been mine. I'm outgrowing freelancers. It's time to hire in order to scale.
Visit caneelian.comWe analyzed Caneelian.com page load time and found that the first response time was 174 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
caneelian.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value5.5 s
19/100
25%
Value5.3 s
58/100
10%
Value50 ms
100/100
30%
Value0
100/100
15%
Value7.0 s
52/100
10%
174 ms
260 ms
32 ms
83 ms
72 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 31% of them (22 requests) were addressed to the original Caneelian.com, 17% (12 requests) were made to Pixel.wp.com and 11% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (556 ms) relates to the external source I1.wp.com.
Page size can be reduced by 442.6 kB (22%)
2.0 MB
1.6 MB
In fact, the total size of Caneelian.com main page is 2.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. 55% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 99.1 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 99.1 kB or 74% of the original size.
Potential reduce by 7.6 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. Caneelian images are well optimized though.
Potential reduce by 98.7 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 98.7 kB or 65% of the original size.
Potential reduce by 237.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. Caneelian.com needs all CSS files to be minified and compressed as it can save up to 237.2 kB or 83% of the original size.
Number of requests can be reduced by 44 (79%)
56
12
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Caneelian. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
caneelian.com
174 ms
www.caneelian.com
260 ms
wp-emoji-release.min.js
32 ms
style.min.css
83 ms
classic-themes.min.css
72 ms
css
34 ms
style.css
118 ms
colors-dark.css
97 ms
social-logos.min.css
76 ms
jetpack.css
120 ms
jquery.min.js
147 ms
jquery-migrate.min.js
110 ms
photon.min.js
111 ms
comment_count.js
126 ms
skip-link-focus-fix.js
141 ms
navigation.js
141 ms
global.js
144 ms
jquery.scrollTo.js
247 ms
twitter-timeline.min.js
248 ms
sharing.min.js
248 ms
e-202436.js
14 ms
atrk.js
93 ms
hands-in-clay-karen-maes-310484.jpg
556 ms
yoga.jpg
245 ms
223918584
400 ms
count.js
234 ms
06920170714_CaneelJoyce_174.jpg
453 ms
diver-1081987_1920.jpg
428 ms
creative-const-2.jpg
407 ms
cropped-gladiolus_AdobeStock_100347577.jpeg
127 ms
loading.gif
92 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsWkDtDM.ttf
173 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhcMWkDtDM.ttf
220 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduh8MKkDtDM.ttf
233 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhrsKkDtDM.ttf
262 ms
nNLGlOfl1OzZ1Yksrf7NTe3mN+KAIu1M6sZ2Ten4tSOXV2YmrnejTFF63+6YO55nCh1tdxy0X5xieS3dIKs955QVFcUfQjyYFwAA
17 ms
social-logos.eot
66 ms
jizMREVItHgc8qDIbSTKq4XkRiUawTk7f45UM9y05oZ8RODFR-M.ttf
273 ms
jizMREVItHgc8qDIbSTKq4XkRiUawTk7f45UM9y05oYiRODFR-M.ttf
272 ms
jizMREVItHgc8qDIbSTKq4XkRiUawTk7f45UM9y05oaiQ-DFR-M.ttf
272 ms
jizMREVItHgc8qDIbSTKq4XkRiUawTk7f45UM9y05ob8Q-DFR-M.ttf
272 ms
widgets.js
145 ms
count.json
143 ms
g.gif
122 ms
graph.facebook.com
174 ms
count.json
127 ms
graph.facebook.com
226 ms
count.json
172 ms
graph.facebook.com
225 ms
count.json
154 ms
graph.facebook.com
253 ms
count.json
169 ms
graph.facebook.com
252 ms
count.json
168 ms
graph.facebook.com
252 ms
g.gif
117 ms
g.gif
116 ms
g.gif
116 ms
g.gif
115 ms
g.gif
116 ms
g.gif
116 ms
g.gif
116 ms
g.gif
117 ms
g.gif
116 ms
g.gif
118 ms
g.gif
117 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
58 ms
settings
112 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
3 ms
api.js
13 ms
caneelian.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
caneelian.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
caneelian.com 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 Caneelian.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 Caneelian.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.
caneelian.com
Open Graph data is detected on the main page of Caneelian. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: