3.8 sec in total
921 ms
2.8 sec
85 ms
Click here to check amazing Makro content for South Africa. Otherwise, check out these important facts you probably never knew about makro.co.za
Visit makro.co.zaWe analyzed Makro.co.za page load time and found that the first response time was 921 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
makro.co.za performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value19.6 s
0/100
25%
Value15.7 s
0/100
10%
Value8,060 ms
0/100
30%
Value0.049
99/100
15%
Value27.1 s
0/100
10%
921 ms
774 ms
165 ms
529 ms
127 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 43% of them (20 requests) were addressed to the original Makro.co.za, 7% (3 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Analytics.tiktok.com. The less responsive or slowest element that took the longest time to load (921 ms) belongs to the original domain Makro.co.za.
Page size can be reduced by 708.4 kB (56%)
1.3 MB
558.7 kB
In fact, the total size of Makro.co.za main page is 1.3 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. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 55.5 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 55.5 kB or 53% of the original size.
Potential reduce by 653.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 653.0 kB or 56% of the original size.
Number of requests can be reduced by 37 (86%)
43
6
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Makro. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and as a result speed up the page load time.
makro.co.za
921 ms
www.makro.co.za
774 ms
gtm.js
165 ms
init.js
529 ms
core.js+ssdomvar.js+generic-adapter.js
127 ms
bv.js
23 ms
runtimechunk~main.e96c56f94194d908f9e8.js
43 ms
8251.51e407f03a862a81602f.js
24 ms
6443.15c43a107398bf5520e7.js
24 ms
7155.be2a418e9e7e5ddbd798.js
76 ms
8447.2d0cc76768d5f11dd38f.js
38 ms
4066.f854e149064c70dbf742.js
39 ms
7574.b864e58b6e089146967f.js
56 ms
7196.63da1d308ca1fc5a2eb4.js
55 ms
6706.2e183c244b56748a281d.js
55 ms
8395.af18b759a2c2a3f011b9.js
72 ms
2247.bf749b534cafa9fa4200.js
82 ms
5407.695316e92148a8e1a49b.js
123 ms
main-d5ef20ee.8e26cfd27f4823cb57b5.js
87 ms
main-e0718b93.64c72f952ac5693c6f44.js
107 ms
main-b0fa4ddb.146b0d1f884f04243f61.js
100 ms
js
94 ms
uwt.js
269 ms
analytics.js
261 ms
destination
252 ms
bat.js
385 ms
hotjar-2957664.js
428 ms
lN3rYe6yZZ13OspFwlFl.js
421 ms
fbevents.js
337 ms
DhPixel.js
796 ms
ins.js
392 ms
vicinity-tracker.js
368 ms
events.js
426 ms
insight.min.js
408 ms
collect
89 ms
activityi;src=10119546;type=undefined;cat=undefined;ord=1731750923278;npa=0;auiddc=258702738.1714852202;pscdl=noapi;gtm=45fe4510z879327359za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.makro.co.za%2F
167 ms
adsct
149 ms
adsct
233 ms
adsct
142 ms
adsct
165 ms
collect
57 ms
modules.842bcec28f9fd12bb79e.js
37 ms
api
103 ms
ga-audiences
87 ms
main.MTIyYzc3NzllNA.js
23 ms
src=10119546;type=undefined;cat=undefined;ord=1731750923278;npa=0;auiddc=*;pscdl=noapi;gtm=45fe4510z879327359za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.makro.co.za%2F
78 ms
makro.co.za accessibility score
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.
makro.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
makro.co.za 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Makro.co.za 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 Makro.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.
makro.co.za
Open Graph description is not detected on the main page of Makro. 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: