8 sec in total
1.1 sec
6.5 sec
362 ms
Visit zeda.co.za now to see the best up-to-date Zeda content and also check out these interesting facts you probably never knew about zeda.co.za
Visit zeda.co.zaWe analyzed Zeda.co.za page load time and found that the first response time was 1.1 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
zeda.co.za performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value10.2 s
0/100
25%
Value11.2 s
5/100
10%
Value600 ms
49/100
30%
Value0
100/100
15%
Value11.0 s
21/100
10%
1134 ms
156 ms
450 ms
674 ms
900 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 75% of them (76 requests) were addressed to the original Zeda.co.za, 12% (12 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Irhosted.profiledata.co.za. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Zeda.co.za.
Page size can be reduced by 102.0 kB (62%)
165.3 kB
63.3 kB
In fact, the total size of Zeda.co.za main page is 165.3 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. 70% of websites need less resources to load. HTML takes 117.3 kB which makes up the majority of the site volume.
Potential reduce by 97.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 97.8 kB or 83% of the original size.
Potential reduce by 2.8 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, Zeda needs image optimization as it can save up to 2.8 kB or 41% 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 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. This website has mostly compressed JavaScripts.
Potential reduce by 396 B
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. Zeda.co.za needs all CSS files to be minified and compressed as it can save up to 396 B or 44% of the original size.
Number of requests can be reduced by 62 (84%)
74
12
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zeda. 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 from 31 to 1 for CSS and as a result speed up the page load time.
zeda.co.za
1134 ms
script.js
156 ms
all.min.css
450 ms
simple-line-icons.min.css
674 ms
style.min.css
900 ms
hamburgers.min.css
676 ms
collapse.css
674 ms
aa4cd108caefe67bed556707fc45a33f.css
677 ms
elementor-icons.min.css
677 ms
frontend-lite.min.css
1121 ms
swiper.min.css
896 ms
post-105.css
895 ms
slider-y.css
896 ms
frontend-lite.min.css
908 ms
post-15.css
1119 ms
general.min.css
1118 ms
widgets.css
1125 ms
style.min.css
1129 ms
css
34 ms
fontawesome.min.css
1131 ms
solid.min.css
1341 ms
regular.min.css
1341 ms
jquery.min.js
1570 ms
jquery-migrate.min.js
1346 ms
js
75 ms
log
400 ms
widget-icon-list.min.css
1131 ms
widget-flip-box.min.css
1135 ms
post-1850.css
1347 ms
post-1854.css
1348 ms
post-1857.css
1349 ms
slider-y.js
1486 ms
imagesloaded.min.js
1487 ms
theme.min.js
1570 ms
full-screen-mobile-menu.min.js
1573 ms
magnific-popup.min.js
1578 ms
ow-lightbox.min.js
1580 ms
flickity.pkgd.min.js
1585 ms
ow-slider.min.js
1593 ms
scroll-effect.min.js
1793 ms
scroll-top.min.js
1794 ms
select.min.js
1567 ms
general.min.js
1348 ms
slick.min.js
1356 ms
main.min.js
1355 ms
webpack-pro.runtime.min.js
1562 ms
webpack.runtime.min.js
1559 ms
frontend-modules.min.js
1346 ms
wp-polyfill-inert.min.js
1345 ms
font-awesome.min.css
28 ms
css2
18 ms
slick.css
26 ms
slick-theme.css
34 ms
regenerator-runtime.min.js
1368 ms
wp-polyfill.min.js
1360 ms
hooks.min.js
1553 ms
i18n.min.js
1343 ms
frontend.min.js
1346 ms
waypoints.min.js
1341 ms
core.min.js
1343 ms
frontend.min.js
1344 ms
elements-handlers.min.js
1551 ms
jquery.sticky.min.js
1338 ms
t02_intraday.html
1287 ms
Zeda-Logo-Landscape.png
1270 ms
BANNER_1-scaled.webp
1714 ms
Zeda-IR-Web-banner-2024-01-1024x794.webp
1275 ms
Avis.png
1062 ms
budget-logo-small.png
1267 ms
avis-fleet-logo-small.png
1268 ms
avis-car-sales-logo-small.png
1280 ms
Video.webp
1649 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
23 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
34 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
1423 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
33 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
1434 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
33 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
31 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
33 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
34 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
36 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
36 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
35 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
35 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
1352 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
1375 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
1554 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
1566 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
1554 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
1573 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
1562 ms
fa-solid-900.woff
1572 ms
fa-solid-900.ttf
2227 ms
fa-regular-400.woff
1563 ms
fa-regular-400.ttf
1778 ms
css2
17 ms
scrolling_ticker.css
260 ms
iframeResizer.contentWindow.min.js
514 ms
up_big.png
763 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf
12 ms
zeda.co.za accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
zeda.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
zeda.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
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 Zeda.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 Zeda.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.
zeda.co.za
Open Graph description is not detected on the main page of Zeda. 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: