6.9 sec in total
1.3 sec
5.5 sec
103 ms
Visit wimpy.co.za now to see the best up-to-date Wimpy content for South Africa and also check out these interesting facts you probably never knew about wimpy.co.za
Order breakfast or lunch through the official Wimpy website. Find your nearest restaurant, choose from our range of breakfasts, burgers and premium coffee.
Visit wimpy.co.zaWe analyzed Wimpy.co.za page load time and found that the first response time was 1.3 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
wimpy.co.za performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value8.6 s
1/100
25%
Value9.4 s
12/100
10%
Value2,070 ms
7/100
30%
Value0.042
99/100
15%
Value12.2 s
15/100
10%
1292 ms
32 ms
23 ms
221 ms
434 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 95% of them (73 requests) were addressed to the original Wimpy.co.za, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Wimpy.co.za.
Page size can be reduced by 1.2 MB (33%)
3.7 MB
2.5 MB
In fact, the total size of Wimpy.co.za main page is 3.7 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. 45% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 23.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. This page needs HTML code to be minified as it can gain 4.8 kB, which is 17% 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 23.5 kB or 82% of the original size.
Potential reduce by 290.1 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, Wimpy needs image optimization as it can save up to 290.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 517.6 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 517.6 kB or 70% of the original size.
Potential reduce by 406.4 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. Wimpy.co.za needs all CSS files to be minified and compressed as it can save up to 406.4 kB or 86% of the original size.
Number of requests can be reduced by 32 (44%)
73
41
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wimpy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
wimpy.co.za
1292 ms
jquery.min.js
32 ms
css
23 ms
k2.css
221 ms
widgetkit-56d6cdcd.css
434 ms
menu-da682b05941fe060e74f934e18149662.css
439 ms
menu-hovers-da682b05941fe060e74f934e18149662.css
450 ms
grid-responsive.css
437 ms
grid-responsive.css
441 ms
bootstrap.css
656 ms
master-fb38d4ac63c526e49c39abe465590a38.css
869 ms
mediaqueries.css
648 ms
uikitanimations.css
649 ms
settings.css
699 ms
captions.css
697 ms
mootools-core.js
868 ms
core.js
663 ms
jquery.min.js
1298 ms
jquery-noconflict.js
863 ms
jquery-migrate.min.js
889 ms
k2.js
890 ms
caption.js
1078 ms
widgetkit-ead474af.js
1084 ms
mootools-more.js
1561 ms
gantry-totop.js
1085 ms
bootstrap.min.js
1094 ms
browser-engines.js
1292 ms
destinyfx.js
1298 ms
totop.js
1300 ms
uikit.min.js
1312 ms
rokmediaqueries.js
1509 ms
jquery.themepunch.plugins.min.js
698 ms
jquery.themepunch.revolution.min.js
699 ms
style.css
648 ms
lightbox.js
220 ms
mediaelement-and-player.js
236 ms
spotlight.js
231 ms
analytics.js
72 ms
doubleBack.jpg
907 ms
copyDoubleup.png
248 ms
plate2.png
1119 ms
plate1.png
1544 ms
priceBouleup.png
874 ms
breakfastBack.jpg
2194 ms
price.png
964 ms
burgerBack.jpg
1747 ms
price.png
1128 ms
VS-slider-bg.jpg
1836 ms
vs-slider-circle.png
1667 ms
vs-slider-hash.png
1361 ms
24606_Wimpy-Kids-main-web-slider_bg.png
2046 ms
24606_Wimpy-Kids-main-web-slider_img1.png
1787 ms
24606_Wimpy-Kids-main-web-slider_img2.png
1888 ms
24606_Wimpy-Kids-main-web-slider_logo.png
1964 ms
24606_Wimpy-Kids-main-web-slider_text.png
2013 ms
30563-Wimpy-Rituals-Promo---2nd-Cup-on-us-Web-Mailer-Gen_bg.jpg
2061 ms
30563-Wimpy-Rituals-Promo---2nd-Cup-on-us-Web-Mailer-Gen_title.jpg
2118 ms
30563-Wimpy-Rituals-Promo---2nd-Cup-on-us-Web-Mailer-Gen_txt.png
2184 ms
Wimpy_logo.png
217 ms
icon-add.png
217 ms
icon-locator.png
217 ms
icon-promo.png
373 ms
icon-contact.png
374 ms
icon_doubleUpSummer.png
377 ms
icon_doubleUpSummer.png
459 ms
icon-add.png
476 ms
icon-locator.png
475 ms
icon-promo.png
594 ms
icon-contact.png
607 ms
timer.png
2186 ms
loader.gif
2203 ms
fontawesome-webfont.woff
777 ms
museo_slab_900-webfont.woff
1150 ms
museo_slab_900-webfont.woff
854 ms
collect
25 ms
museo_slab_900-webfont.ttf
676 ms
museo_slab_900-webfont.svg
661 ms
wimpy.co.za accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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.
wimpy.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
wimpy.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 Wimpy.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 Wimpy.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.
wimpy.co.za
Open Graph description is not detected on the main page of Wimpy. 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: