15.9 sec in total
7.1 sec
8.6 sec
215 ms
Welcome to xmall.com.ng homepage info - get ready to check Xmall best content right away, or after learning these important things about xmall.com.ng
For premium product
Visit xmall.com.ngWe analyzed Xmall.com.ng page load time and found that the first response time was 7.1 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
xmall.com.ng performance score
7144 ms
113 ms
126 ms
130 ms
120 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 43% of them (60 requests) were addressed to the original Xmall.com.ng, 25% (35 requests) were made to Maps.google.com and 6% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (7.1 sec) belongs to the original domain Xmall.com.ng.
Page size can be reduced by 1.4 MB (65%)
2.2 MB
757.8 kB
In fact, the total size of Xmall.com.ng main page is 2.2 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. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 70.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 70.4 kB or 84% of the original size.
Potential reduce by 59.3 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, Xmall needs image optimization as it can save up to 59.3 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.0 MB
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 1.0 MB or 71% of the original size.
Potential reduce by 296.5 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. Xmall.com.ng needs all CSS files to be minified and compressed as it can save up to 296.5 kB or 88% of the original size.
Number of requests can be reduced by 94 (72%)
130
36
The browser has sent 130 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xmall. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
xmall.com.ng
7144 ms
wp-emoji-release.min.js
113 ms
events_manager.css
126 ms
settings.css
130 ms
colorbox.css
120 ms
jquery-selectbox.css
133 ms
style.css
199 ms
responsive.css
183 ms
font-awesome.min.css
254 ms
images.css
235 ms
color.css
188 ms
jquery.js
291 ms
jquery-migrate.min.js
250 ms
core.min.js
265 ms
widget.min.js
275 ms
position.min.js
312 ms
mouse.min.js
314 ms
sortable.min.js
314 ms
datepicker.min.js
318 ms
menu.min.js
348 ms
autocomplete.min.js
352 ms
resizable.min.js
344 ms
draggable.min.js
355 ms
button.min.js
356 ms
dialog.min.js
404 ms
events-manager.js
407 ms
jquery.themepunch.tools.min.js
511 ms
jquery.themepunch.revolution.min.js
427 ms
css
62 ms
js
47 ms
jquery-ui-1.10.4.custom.min.js
132 ms
jquery.colorbox-min.js
66 ms
jquery.flexslider-min.js
64 ms
jquery.selectbox-0.6.1.js
63 ms
jquery.tweet.js
101 ms
jquery.mobilemenu.min.js
114 ms
jquery.placeholder.min.js
114 ms
jquery.ui.autocomplete.min.js
112 ms
jquery.sheepItPlugin.js
167 ms
jquery.gomap-1.3.2.min.js
167 ms
jquery.gmap.min.js
179 ms
map.js
179 ms
markerclusterer.js
178 ms
ajax_search.js
180 ms
jflickrfeed.min.js
226 ms
superfish.js
227 ms
rating.js
228 ms
scripts.js
228 ms
comment-reply.min.js
229 ms
pix.png
178 ms
logo-mall.png
278 ms
2.png
264 ms
contact.jpg
265 ms
pix-adv.png
258 ms
trobber.gif
261 ms
partner-1.jpg
246 ms
xmall.com.ng
1171 ms
partner-5.jpg
247 ms
partner-2.jpg
251 ms
fontawesome-webfont.woff
292 ms
I1Pn3gihk5vyP0Yw5GqKsQ.woff
60 ms
7DI7Kjvwfuz8m3ExKe6m-Q.woff
69 ms
1bHRUMxmJHoup12DnI9XmQ.woff
107 ms
kU6VHbqMAZhaN_nXCmLQsQ.woff
84 ms
widgets.js
101 ms
common.js
30 ms
util.js
53 ms
geocoder.js
53 ms
map.js
58 ms
overlay.js
58 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
252 ms
overlay.png
104 ms
onion.js
21 ms
openhand_8_8.cur
139 ms
ViewportInfoService.GetViewportInfo
270 ms
stats.js
47 ms
controls.js
41 ms
marker.js
36 ms
ViewportInfoService.GetViewportInfo
282 ms
css
126 ms
transparent.png
111 ms
google4.png
106 ms
mapcnt6.png
72 ms
sv5.png
105 ms
pix-map.png
93 ms
tmapctrl.png
87 ms
tmapctrl4.png
87 ms
arrow-down.png
98 ms
imgs8.png
129 ms
syndication
205 ms
377042022453899264
272 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
36 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
34 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
35 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
36 ms
vt
53 ms
vt
37 ms
vt
31 ms
vt
30 ms
vt
34 ms
vt
32 ms
vt
47 ms
vt
49 ms
vt
58 ms
vt
53 ms
vt
56 ms
vt
54 ms
vt
63 ms
vt
67 ms
vt
79 ms
vt
77 ms
vt
79 ms
vt
172 ms
vt
79 ms
vt
85 ms
vt
89 ms
vt
98 ms
vt
95 ms
vt
99 ms
vt
115 ms
proxy.jpg
67 ms
proxy.jpg
62 ms
proxy.jpg
58 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
59 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
77 ms
OkBPLclQ_normal.jpeg
23 ms
AuthenticationService.Authenticate
175 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
42 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
36 ms
proxy.jpg
4 ms
proxy.jpg
3 ms
proxy.jpg
5 ms
photos_public.gne
133 ms
jot.html
27 ms
15647274066_2ee48c3fe9_s.jpg
32 ms
15484954949_a4e97a9dc5_s.jpg
38 ms
15647103116_1e4b9033f0_s.jpg
34 ms
15485436268_846ccca178_s.jpg
38 ms
15668911091_4ef20118b5_s.jpg
47 ms
15668909741_eaf3db4054_s.jpg
40 ms
xmall.com.ng SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xmall.com.ng 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 Xmall.com.ng 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.
xmall.com.ng
Open Graph description is not detected on the main page of Xmall. 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: