2.5 sec in total
160 ms
1.5 sec
808 ms
Click here to check amazing Annabelle content for Canada. Otherwise, check out these important facts you probably never knew about annabelle.com
Visit annabelle.comWe analyzed Annabelle.com page load time and found that the first response time was 160 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
annabelle.com performance score
name
value
score
weighting
Value10.2 s
0/100
10%
Value22.2 s
0/100
25%
Value10.5 s
8/100
10%
Value550 ms
53/100
30%
Value0
100/100
15%
Value17.4 s
4/100
10%
160 ms
28 ms
34 ms
35 ms
36 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 79% of them (95 requests) were addressed to the original Annabelle.com, 8% (9 requests) were made to Scontent.xx.fbcdn.net and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (495 ms) belongs to the original domain Annabelle.com.
Page size can be reduced by 1.6 MB (36%)
4.4 MB
2.8 MB
In fact, the total size of Annabelle.com main page is 4.4 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 2.4 MB which makes up the majority of the site volume.
Potential reduce by 164.3 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 59.0 kB, which is 32% 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 164.3 kB or 91% of the original size.
Potential reduce by 87.5 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. Annabelle images are well optimized though.
Potential reduce by 785.4 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 785.4 kB or 71% of the original size.
Potential reduce by 547.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. Annabelle.com needs all CSS files to be minified and compressed as it can save up to 547.9 kB or 87% of the original size.
Number of requests can be reduced by 69 (62%)
112
43
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Annabelle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
www.annabelle.com
160 ms
css
28 ms
jquery.fancybox.css
34 ms
ajaxaddto.css
35 ms
owl.carousel.css
36 ms
calendar-win2k-1.css
36 ms
owl.transitions.css
37 ms
bootstrap-theme.min.css
40 ms
bootstrap.min.css
78 ms
styles.css
111 ms
widgets.css
71 ms
simple.css
72 ms
mirasvit_seo.css
72 ms
style.css
74 ms
style.css
99 ms
font-awesome.min.css
101 ms
cat-icon.css
103 ms
megamenu.css
105 ms
megamenu_responsive.css
135 ms
styles.css
136 ms
style.css
136 ms
setting_en_ca.css
136 ms
design_en_ca.css
137 ms
custom.css
139 ms
prototype.js
157 ms
ccard.js
176 ms
validation.js
177 ms
builder.js
178 ms
effects.js
179 ms
dragdrop.js
182 ms
controls.js
190 ms
slider.js
189 ms
js.js
194 ms
form.js
192 ms
menu.js
192 ms
translate.js
196 ms
cookies.js
218 ms
1516433553.js
233 ms
campaignCatcher.js
208 ms
ga.js
199 ms
simple.js
200 ms
jquery-1.10.2.min.js
220 ms
jquery-noconflict.js
205 ms
jquery.fancybox.js
243 ms
ajaxaddto.js
237 ms
jquery.elevatezoom.js
212 ms
owl.carousel.min.js
204 ms
product.js
213 ms
configurable.js
213 ms
calendar.js
209 ms
calendar-setup.js
198 ms
jquery-migrate-1.0.0.js
195 ms
bootstrap.min.js
197 ms
instafeed.min.js
200 ms
swatches-product.js
179 ms
jquery.swblog.js
188 ms
megamenu.js
190 ms
bundle.js
191 ms
sw_quickview.js
190 ms
twitterfetcher.js
181 ms
modernizr.custom.min.js
196 ms
enquire.js
177 ms
app.js
178 ms
imagesloaded.js
179 ms
jquery.granada.js
180 ms
waypoints.min.js
180 ms
event
59 ms
brandon-regular.otf
115 ms
ga.js
12 ms
gtm.js
63 ms
fbevents.js
62 ms
goal.min.js
24 ms
logo_annabelle_en_trans.png
59 ms
12369101_10153624318541321_3883331404902488737_n.jpg
170 ms
lacquers_en.jpg
365 ms
eyeliners_en.jpg
192 ms
palette_en.jpg
214 ms
chrome_mobile.jpg
141 ms
lacquer_mobile.jpg
190 ms
liner_mobile.jpg
213 ms
palette_mobile.jpg
362 ms
ajax-loader.gif
236 ms
i_asc_arrow.gif
237 ms
annabelle_eyeliner_chromekohl_goldybrown.jpg
362 ms
annabelle_eyeliner_chromekohl_purpledaze.jpg
362 ms
annabelle_eyeliner_chromekohl_sparklingblue.jpg
364 ms
annabelle_eyeliner_chromekohl_shockingcharcoal.jpg
364 ms
annabelle_eyeliner_chromekohl_silverrush.jpg
365 ms
annabelle_eyeliner_chromekohl_frostyturquoise.jpg
367 ms
069783688911_enfr_01_front.jpg
413 ms
069783688928_enfr_01_front.jpg
412 ms
069783688935_enfr_01_front.jpg
411 ms
069783688942_enfr_01_front_1.jpg
412 ms
069783688959_enfr_01_front.jpg
422 ms
069783688966_enfr_01_front.jpg
422 ms
annabelle_waterproofliquideyeliner_blackstar_jpg_0667031.jpg
444 ms
annabelle_waterproofliquideyeliner_bronze_jpg_0667032.jpg
432 ms
annabelle_waterproofliquideyeliner_bluespark_jpg_0667033.jpg
435 ms
069783691010-enfr-01-front_1.jpg
495 ms
loader.gif
448 ms
12803051_10153787417951321_8502231748476668228_n.jpg
163 ms
12308261_10207801320926743_1291132813065604868_n.jpg
71 ms
10009763_994182710597773_1610676707564272202_n.jpg
128 ms
421308_102973603167055_776319542_n.jpg
132 ms
12814399_10208737859434079_5680018320919993941_n.jpg
132 ms
12495020_10156435353205387_2081145838949223083_n.jpg
133 ms
12321593_10207365025100728_3209107064352680421_n.jpg
131 ms
10346309_10203958047013118_3058314811477635821_n.jpg
133 ms
__utm.gif
28 ms
granada-font.woff
437 ms
brandon-bold.otf
484 ms
DXI1ORHCpsQm3Vp6mXoaTRa1RVmPjeKy21_GQJaLlJI.woff
19 ms
u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff
22 ms
k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff
37 ms
84 ms
collect
108 ms
recent
487 ms
MasterTMS.min.js
119 ms
tags
15 ms
print.css
21 ms
annabelle.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
Links do not have a discernible name
annabelle.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
annabelle.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
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Annabelle.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 Annabelle.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.
annabelle.com
Open Graph description is not detected on the main page of Annabelle. 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: