3.3 sec in total
162 ms
2.9 sec
262 ms
Click here to check amazing Oxcandystore content for India. Otherwise, check out these important facts you probably never knew about oxcandystore.com
Oxwall CandyStore community
Visit oxcandystore.comWe analyzed Oxcandystore.com page load time and found that the first response time was 162 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
oxcandystore.com performance score
162 ms
1213 ms
238 ms
429 ms
235 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 49% of them (33 requests) were addressed to the original Oxcandystore.com, 15% (10 requests) were made to Apis.google.com and 10% (7 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Oxcandystore.com.
Page size can be reduced by 389.0 kB (42%)
926.2 kB
537.2 kB
In fact, the total size of Oxcandystore.com main page is 926.2 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. 65% of websites need less resources to load. Images take 486.8 kB which makes up the majority of the site volume.
Potential reduce by 20.8 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 20.8 kB or 77% of the original size.
Potential reduce by 57.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. Obviously, Oxcandystore needs image optimization as it can save up to 57.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 176.2 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 176.2 kB or 69% of the original size.
Potential reduce by 134.4 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. Oxcandystore.com needs all CSS files to be minified and compressed as it can save up to 134.4 kB or 86% of the original size.
Number of requests can be reduced by 33 (52%)
63
30
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oxcandystore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
oxcandystore.com
162 ms
oxcandystore.com
1213 ms
ow.css
238 ms
base.css
429 ms
style.css
235 ms
rhinoslider-1.05.css
233 ms
jquery-1.7.1.min.js
446 ms
platform.js
49 ms
json2.js
254 ms
ow.js
521 ms
rhinoslider-1.05.min.js
364 ms
jquery.mousewheel.js
313 ms
jquery.jscrollpane.js
393 ms
console.js
410 ms
bg.jpg
144 ms
ic_lens.png
142 ms
console.png
144 ms
oxwallcandystore-logo.png
142 ms
01.jpg
239 ms
mottoline_bg.png
149 ms
item_promo_thumb_19_126_1408776350.jpg
303 ms
item_promo_thumb_18_119_1407427196.jpg
406 ms
item_promo_thumb_15_13_1382866319.jpg
406 ms
item_promo_thumb_10_10_1382801742.jpg
405 ms
item_promo_thumb_9_12_1382865252.jpg
304 ms
item_promo_thumb_14_7_1382796063.jpg
388 ms
widgets.js
183 ms
museosans_500-webfont.woff
395 ms
museo500-regular-webfont.woff
395 ms
likebox.php
215 ms
bicon-heart.png
391 ms
bicon-quality.png
485 ms
bicon-support.png
485 ms
box-shadow-small.png
485 ms
cb=gapi.loaded_0
12 ms
cb=gapi.loaded_1
30 ms
page
200 ms
ga.js
53 ms
postmessageRelay
105 ms
left-arrow.png
360 ms
right-arrow.png
362 ms
__utm.gif
20 ms
api.js
70 ms
core:rpc:shindig.random:shindig.sha1.js
200 ms
2536007149-postmessagerelay.js
71 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
65 ms
n7IAcY2jJIh.css
339 ms
_rx8naC75Dy.js
540 ms
x5F9OMjKyLw.js
675 ms
ICDbTSzjQEg.js
557 ms
TTCre3391I0.js
558 ms
rs=AGLTcCMdi7G7uTganqcTTVz4zIZq7G5wNA
14 ms
rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA
23 ms
rs=AGLTcCNDCD2FX1GmFI4h9QOi1JonWtDyWA
77 ms
photo.jpg
230 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
153 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
161 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
199 ms
syndication
201 ms
503589143612379138
245 ms
rs=AGLTcCNDCD2FX1GmFI4h9QOi1JonWtDyWA
53 ms
rs=AGLTcCNDCD2FX1GmFI4h9QOi1JonWtDyWA
16 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
31 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
59 ms
2IqeObqi_normal.jpeg
37 ms
jot
40 ms
I6-MnjEovm5.js
69 ms
vlXaquuXMrr.js
74 ms
oxcandystore.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oxcandystore.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 Oxcandystore.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.
oxcandystore.com
Open Graph description is not detected on the main page of Oxcandystore. 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: