7.1 sec in total
224 ms
6.2 sec
605 ms
Click here to check amazing Slurpee content for Australia. Otherwise, check out these important facts you probably never knew about slurpee.com.au
Check out the latest and greatest Slurpee flavours at 7-Eleven, including our Slurpee low sugar range. No one does chilled flavours like Slurpee!
Visit slurpee.com.auWe analyzed Slurpee.com.au page load time and found that the first response time was 224 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
slurpee.com.au performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value16.1 s
0/100
25%
Value10.5 s
8/100
10%
Value1,950 ms
8/100
30%
Value0.001
100/100
15%
Value34.2 s
0/100
10%
224 ms
12 ms
18 ms
536 ms
217 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 39% of them (42 requests) were addressed to the original Slurpee.com.au, 33% (35 requests) were made to Static.xx.fbcdn.net and 9% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Scontent.cdninstagram.com.
Page size can be reduced by 391.4 kB (20%)
1.9 MB
1.5 MB
In fact, the total size of Slurpee.com.au main page is 1.9 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 46.3 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 46.3 kB or 69% of the original size.
Potential reduce by 32.7 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. Slurpee images are well optimized though.
Potential reduce by 312.4 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 312.4 kB or 63% of the original size.
Number of requests can be reduced by 49 (47%)
104
55
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Slurpee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.slurpee.com.au
224 ms
reset-min.css
12 ms
main.css
18 ms
prettyPhoto.css
536 ms
sIFR-screen.css
217 ms
sIFR-flavours.css
72 ms
jquery-1.3.2.min.js
41 ms
jquery.prettyPhoto.js
24 ms
browser.js
38 ms
sifr.js
87 ms
addthis_widget.js
67 ms
css
353 ms
ga.js
191 ms
ad_radar.php
159 ms
12599415_1144009062298228_940900164_n.jpg
1766 ms
63d380329b25d7615416f27f6d26bae98737d4f6.gif
52 ms
e96648c661ff8e6454f9c79d3d85ac790d39d88c.jpg
376 ms
hd-nav-bg2.png
214 ms
hd-nav-sprites-zilched.png
149 ms
hd-social-sprites.png
147 ms
5fe24226557b19a613c274874b084c23395e8c36.jpg
147 ms
s_0957952359c669923ab7b2e7ed51bbadd8315be1.png
369 ms
66bfc3dd649979f53760e9e8b4f83c77b1fef0c4.jpg
572 ms
web-slurps-logo-facebook.png
373 ms
web-slurps-logo-youtube.png
373 ms
default.jpg
372 ms
default.jpg
373 ms
default.jpg
440 ms
all.js
472 ms
side-flavour-flavours-bg.png
519 ms
side-flavour-dispenser.png
549 ms
04-2016.jpg
674 ms
side-news-bg.png
691 ms
side-news-view-sprites.png
546 ms
side-news-bullet.png
608 ms
main-promo-video-bg.png
916 ms
web-slurps-hd.png
745 ms
web-slurps-cn.png
913 ms
web-slurps-statuses-hd.png
696 ms
web-slurps-statuses-cn.png
775 ms
web-slurps-statuses-main.png
735 ms
web-slurps-button-sprites.png
745 ms
web-slurps-statuses-ft.png
809 ms
web-slurps-youtube-bg.png
820 ms
web-slurps-ft.png
845 ms
instagram_background.png
1111 ms
fbds.js
531 ms
aee263decd529d5ab9618c9352afb0dbe0062d47.gif
835 ms
store-btn-small.png
843 ms
rpx.js
173 ms
6ozZp4BPlrbDRWPe3EBGAzcaOoGrwtJRci4wjFnSRpA.woff
486 ms
__utm.gif
169 ms
300lo.json
1239 ms
sh.953eb77977227bfd253ee158.html
72 ms
ie67-css.6ce70fa163f64a2f3bc9.js
108 ms
189 ms
xd_arbiter.php
312 ms
xd_arbiter.php
561 ms
173 ms
ping
13 ms
10 ms
like_box.php
134 ms
84vXxQwQw92.css
295 ms
R2ZPh6fd7GC.css
367 ms
gxZYrzUnHwF.css
467 ms
pbfGFiJ8-ud.css
663 ms
2yfgmjUXJXS.css
649 ms
KnTqNe4e7Mj.css
570 ms
K7BfA_NW6LN.css
679 ms
SRSW8M763HA.js
752 ms
ullQFyhrQFI.js
777 ms
y97Ig99UVTs.js
678 ms
KHAtULXOQuz.js
728 ms
W4NL_XloU4d.js
727 ms
eACiSk3I2K6.js
736 ms
FOagnU9QnXq.js
821 ms
rR4Qw0p7TFQ.js
1061 ms
ULtnh-HfQSw.js
803 ms
6IFzBT9uHU-.js
911 ms
CFl9V4qErDd.js
938 ms
xEc-vrRFOUC.js
828 ms
i8XO-4kv8i7.js
906 ms
In8KOzYgNHs.js
910 ms
Cw6QosZRsiU.js
917 ms
d_-F4IIjJo3.js
983 ms
RVrf1FEV-oX.js
985 ms
12744688_10153929305883638_6717824718320499418_n.png
791 ms
12814665_10153929306798638_6511874011399815921_n.png
906 ms
12933117_10154037834203638_8113758431201089738_n.png
1755 ms
12919713_10154037821643638_1327639087484006018_n.jpg
1363 ms
12670674_10154026120378638_4231158583667464065_n.jpg
1112 ms
12932881_10154026120348638_6717000034092447756_n.jpg
1092 ms
12923124_10154026119378638_7972227173403680171_n.jpg
1091 ms
12923175_10154026120633638_6078372175976659796_n.jpg
1254 ms
1916154_10153972969808638_1555135298742738852_n.jpg
1456 ms
12105567_10153983077883638_126701762_n.jpg
1232 ms
hdYxvZtlnwH.png
123 ms
wL6VQj7Ab77.png
120 ms
1JLnMyDN79z.png
122 ms
pimRBh7B6ER.png
124 ms
ex8r-_gkt_Y.png
455 ms
Hr6TmypuQJw.png
123 ms
gm-8CYVMZ_l.png
206 ms
S4NGepoqhZB.js
108 ms
ye4Amg-qrtc.js
164 ms
QbRMFx7-fCZ.png
100 ms
VXcANLwwL5J.js
93 ms
slurpee.com.au 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
ARIA IDs are not unique
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
Buttons do not have an accessible name
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
slurpee.com.au 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
Missing source maps for large first-party JavaScript
slurpee.com.au 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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Slurpee.com.au 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 Slurpee.com.au 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.
slurpee.com.au
Open Graph description is not detected on the main page of Slurpee. 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: