4.3 sec in total
142 ms
3.6 sec
542 ms
Visit loot.co.za now to see the best up-to-date Loot content for South Africa and also check out these interesting facts you probably never knew about loot.co.za
Browse | All Departments All Departments
Visit loot.co.zaWe analyzed Loot.co.za page load time and found that the first response time was 142 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
loot.co.za performance score
name
value
score
weighting
Value4.5 s
16/100
10%
Value24.3 s
0/100
25%
Value16.9 s
0/100
10%
Value4,520 ms
0/100
30%
Value0.255
48/100
15%
Value23.9 s
1/100
10%
142 ms
2244 ms
74 ms
125 ms
60 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 29% of them (31 requests) were addressed to the original Loot.co.za, 25% (26 requests) were made to Media.loot.co.za and 23% (24 requests) were made to Cdnv3.loot.co.za. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Loot.co.za.
Page size can be reduced by 1.3 MB (85%)
1.5 MB
225.2 kB
In fact, the total size of Loot.co.za main page is 1.5 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. 65% of websites need less resources to load. HTML takes 1.2 MB which makes up the majority of the site volume.
Potential reduce by 1.1 MB
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 1.1 MB or 93% of the original size.
Potential reduce by 183.0 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 183.0 kB or 56% of the original size.
Number of requests can be reduced by 41 (82%)
50
9
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Loot. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and as a result speed up the page load time.
loot.co.za
142 ms
www.loot.co.za
2244 ms
gtm.js
74 ms
gtm.js
125 ms
bootstrap.min.css
60 ms
react-datepicker.css
69 ms
react-datepicker-cssmodules.css
141 ms
rc-steps.css
120 ms
default.css
114 ms
loot.co.za.css
115 ms
polyfill.min.js
43 ms
slick.min.css
116 ms
slick-theme.min.css
118 ms
addtohomescreen.css
114 ms
addtohomescreen.js
116 ms
db820cde3c081ed9d652.css
297 ms
9548fff6599745692b2e.css
486 ms
e4958afce9c990332b0f.css
488 ms
Verimark_LHS.gif
254 ms
Marketplace.svg
407 ms
loot_logo.svg
201 ms
Cart.svg
201 ms
Account.svg
202 ms
MagnifyingGlass.svg
201 ms
Orders.svg
201 ms
Heart.svg
214 ms
Help.svg
358 ms
ArrowRight.svg
358 ms
PlainArrowLeft.svg
357 ms
PlainArrowRight.svg
348 ms
youtube-svgrepo-com.svg
345 ms
twitter-svgrepo-com.svg
406 ms
facebook-svgrepo-com.svg
458 ms
instagram_round_icon_social_media_icon.svg
471 ms
Sewing_1_LHS.gif
402 ms
Cricut_LHS.gif
450 ms
PowerYourAdventures1_LHS.jpg
451 ms
Bosch_LHS.gif
452 ms
WashingMachines_LHS.gif
453 ms
SkyscraperDelivery.gif
450 ms
Discovery_Web320x129.jpg
471 ms
Pargo2_LHS.jpg
469 ms
ShopNow&Save_JazzFest_Strip.gif
469 ms
MothersDay_Strip.jpg
468 ms
StarWars_Strip.jpeg
470 ms
Skyworth_Circle.png
466 ms
Hisense_Circle.png
584 ms
Toshiba_Circle.png
581 ms
Sinotec_Circle.png
588 ms
ASicillianAffair_Strip.gif
588 ms
Fiction_Circle.png
586 ms
Cookbook_Circle.png
582 ms
Bio_Circle.png
642 ms
Afrikaans_Circle.png
646 ms
PenguinPost_Orange_Strip.jpg
645 ms
MD_Beauty_TrBlock.jpg
641 ms
MD_Stationery_TrBlock.jpg
644 ms
MD_MomToBe_TrBlock.jpg
644 ms
MD_Wearables_TrBlock.jpg
645 ms
js
201 ms
destination
363 ms
analytics.js
428 ms
fbevents.js
425 ms
B10240299.136967104;sz=1x2;ord=[timestamp];dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=
423 ms
events.js
422 ms
polyfills-e479c6e9625ada71bd60.js
260 ms
webpack-50bee04d1dc61f8adf5b.js
506 ms
framework.960580ce158896c55eec.js
505 ms
commons.ee828d27eebaa907c804.js
500 ms
main-63c091429375f029f28e.js
505 ms
_app-685e0197308f823e6adc.js
614 ms
cb1608f2.5a7b7d35c7fbe69a60d8.js
612 ms
75fc9c18.75eca9c35ac7463254d7.js
609 ms
06f6b0c0.4971db34e48472cfdbb8.js
729 ms
4a3ea9cd.783f9151e5220bb97002.js
674 ms
777cf710.fc9b20e7a7aeecc7c231.js
653 ms
a9a7754c.8a6a27b6c9c79c58d3b1.js
682 ms
d8962aca98e9f91f9dd9192b90dcaeaeac4cb569.c927d5c9e21013e2f53f.js
751 ms
72bd61c24d131c7147d2144bf9efd43f697c1995.9ff9fa202bad198c5b7d.js
680 ms
27483898a8b18a76ff0008b2a3320a29df6981d3.20793745e8a5da0ef84f.js
722 ms
b092cf3b6842685402fbe9baa66483d12172cd86.904be9da4d3dd3dd6268.js
746 ms
f360eefae49d5c96bdfd0fba101cc3817864eb65.ca645e17f44756aa98ed.js
893 ms
835446ea7d6610fa5190325b9f0518c3cd11085e.4252c58ca09f29905b8a.js
830 ms
835446ea7d6610fa5190325b9f0518c3cd11085e_CSS.8e0edd9dd9176433ce94.js
792 ms
774f3a5ecb3f40d0915c1d44abc765a8b465ec9f.3eab6c026d2548c2f9a0.js
801 ms
5435b7f03decb202ac2e547b555a38fec11c37f5.cccf19d42dc82166cbcd.js
958 ms
5435b7f03decb202ac2e547b555a38fec11c37f5_CSS.093638bde8598decefe4.js
820 ms
browse-f69ecbe32a516d73f7e7.js
863 ms
_buildManifest.js
872 ms
_ssgManifest.js
890 ms
8ed3761d-3408-4c7b-b314-a3c290746ec4
340 ms
lo.js
329 ms
entrypoint_v2.min.js
502 ms
p3ui32
765 ms
dtm.js
895 ms
destination
92 ms
main.MTIyYzc3NzllNA.js
224 ms
collect
123 ms
collect
171 ms
ufs_web_display.js
133 ms
omrhp.js
162 ms
lo.legacy.js
73 ms
ga-audiences
164 ms
497e64e3
39 ms
xe9aDx.js
38 ms
preload
56 ms
loot.co.za 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
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.
loot.co.za 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
loot.co.za SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Loot.co.za 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Loot.co.za 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.
loot.co.za
Open Graph description is not detected on the main page of Loot. 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: