3.9 sec in total
303 ms
3.4 sec
204 ms
Visit 24eleven.ng now to see the best up-to-date 24 Eleven content and also check out these interesting facts you probably never knew about 24eleven.ng
Online beauty store in Lagos, Nigeria for skincare, makeup, beauty supplements, perfumes and more
Visit 24eleven.ngWe analyzed 24eleven.ng page load time and found that the first response time was 303 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
24eleven.ng performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value4.8 s
30/100
25%
Value4.9 s
65/100
10%
Value780 ms
37/100
30%
Value0.004
100/100
15%
Value12.7 s
13/100
10%
303 ms
577 ms
255 ms
245 ms
234 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 86% of them (114 requests) were addressed to the original 24eleven.ng, 11% (14 requests) were made to Embed.tawk.to and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (577 ms) belongs to the original domain 24eleven.ng.
Page size can be reduced by 399.8 kB (38%)
1.1 MB
662.3 kB
In fact, the total size of 24eleven.ng main page is 1.1 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. 50% of websites need less resources to load. Javascripts take 718.2 kB which makes up the majority of the site volume.
Potential reduce by 143.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. This page needs HTML code to be minified as it can gain 48.9 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 143.4 kB or 93% of the original size.
Potential reduce by 1.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. 24 Eleven images are well optimized though.
Potential reduce by 245.1 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 245.1 kB or 34% of the original size.
Potential reduce by 10.0 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. 24eleven.ng needs all CSS files to be minified and compressed as it can save up to 10.0 kB or 16% of the original size.
Number of requests can be reduced by 96 (76%)
126
30
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 24 Eleven. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 97 to 1 for JavaScripts and as a result speed up the page load time.
24eleven.ng
303 ms
www.24eleven.ng
577 ms
192e767d05023c432b8eeef3b27cd31b.css
255 ms
require.js
245 ms
mixins.js
234 ms
requirejs-config.js
235 ms
adsbygoogle.js
45 ms
24eleven34-01.png
95 ms
img_8050.jpg
94 ms
img_7989_1.jpg
93 ms
img_8063.jpg
94 ms
img_8066.jpg
94 ms
img_8064.jpg
169 ms
img_8070_1.jpg
172 ms
img_7978.jpg
170 ms
img_7986_1_.jpg
170 ms
img_8068.jpg
169 ms
img_8069_1.jpg
247 ms
img_8035.jpg
248 ms
img_7991_1_.jpg
255 ms
hada-labo-serum2.jpg
249 ms
skin-aqua-gel-2024-110g.jpg
250 ms
biore-uv-essence-70g-2023-2.jpg
253 ms
nivea-sun.jpg
325 ms
hatomugi-sun.jpg
325 ms
kose-perfect-gel-120g_1.jpg
333 ms
analytics.js
52 ms
jquery.js
401 ms
jquery.mobile.custom.js
301 ms
responsive.js
302 ms
dataPost.js
362 ms
theme.js
361 ms
bootstrap.js
365 ms
checkout-loader.js
383 ms
translate-inline.js
378 ms
theme1.js
433 ms
translate.js
432 ms
jquery.cookie.js
398 ms
opensans-400.woff
431 ms
opensans-300.woff
439 ms
opensans-600.woff
452 ms
opensans-700.woff
488 ms
Luma-Icons.woff
476 ms
icons-01-2.png
469 ms
icons-06-1.png
504 ms
loader.gif
517 ms
collect
33 ms
default
163 ms
js
73 ms
tabs.js
261 ms
domReady.js
292 ms
matchMedia.js
294 ms
template.js
241 ms
smart-keyboard-handler.js
269 ms
mage.js
277 ms
ie-class-fixer.js
279 ms
main.js
304 ms
jquery-migrate.js
270 ms
common.js
270 ms
jquery-ui.js
430 ms
jquery.storageapi.min.js
279 ms
collapsible.js
160 ms
underscore.js
154 ms
scripts.js
80 ms
text.js
101 ms
js-translation.json
81 ms
print.css
77 ms
twk-arr-find-polyfill.js
177 ms
twk-object-values-polyfill.js
80 ms
twk-event-polyfill.js
259 ms
twk-entries-polyfill.js
86 ms
twk-iterator-polyfill.js
81 ms
twk-promise-polyfill.js
92 ms
twk-main.js
90 ms
twk-vendor.js
98 ms
twk-chunk-vendors.js
102 ms
twk-chunk-common.js
112 ms
twk-runtime.js
111 ms
twk-app.js
174 ms
loader.js
95 ms
page-cache.js
94 ms
app.js
86 ms
form-mini.js
95 ms
click.js
81 ms
cookies.js
90 ms
block-loader.js
158 ms
section-config.js
157 ms
customer-data.js
158 ms
initialize.js
79 ms
types.js
80 ms
layout.js
80 ms
widget-settings
155 ms
knockout.js
167 ms
loader.js
78 ms
knockout-repeat.js
81 ms
knockout-fast-foreach.js
83 ms
knockout-es5.js
87 ms
engine.js
87 ms
scope.js
148 ms
staticChecked.js
153 ms
datepicker.js
158 ms
outer_click.js
174 ms
keyboard.js
174 ms
optgroup.js
224 ms
fadeVisible.js
228 ms
mage-init.js
229 ms
after-render.js
233 ms
i18n.js
238 ms
collapsible.js
239 ms
autoselect.js
299 ms
observable_array.js
301 ms
bound-nodes.js
302 ms
main.js
305 ms
registry.js
314 ms
observable_source.js
229 ms
renderer.js
285 ms
en.js
17 ms
calendar.js
224 ms
block-loader.html
214 ms
wrapper.js
80 ms
events.js
89 ms
es6-collections.js
90 ms
arrays.js
138 ms
compare.js
144 ms
misc.js
146 ms
objects.js
149 ms
strings.js
156 ms
template.js
157 ms
class.js
210 ms
storage.js
213 ms
events.js
214 ms
jquery-ui-timepicker-addon.js
178 ms
loader-1.gif
167 ms
24eleven.ng 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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
24eleven.ng best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
24eleven.ng SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 24eleven.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 24eleven.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.
24eleven.ng
Open Graph description is not detected on the main page of 24 Eleven. 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: