2.1 sec in total
158 ms
1.6 sec
396 ms
Click here to check amazing Fanta content for Romania. Otherwise, check out these important facts you probably never knew about fanta.eu
Give your thirst a taste of the new irresistible Fanta! Check out more of our fruit flavored sodas and limited-edition flavors!
Visit fanta.euWe analyzed Fanta.eu page load time and found that the first response time was 158 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
fanta.eu performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value11.5 s
0/100
25%
Value7.8 s
24/100
10%
Value1,330 ms
17/100
30%
Value2.406
0/100
15%
Value12.0 s
16/100
10%
158 ms
305 ms
90 ms
36 ms
53 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fanta.eu, 71% (96 requests) were made to Fanta.com and 3% (4 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (681 ms) relates to the external source Statse.webtrendslive.com.
Page size can be reduced by 2.6 MB (43%)
6.1 MB
3.5 MB
In fact, the total size of Fanta.eu main page is 6.1 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 176.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. This page needs HTML code to be minified as it can gain 55.8 kB, which is 28% 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 176.3 kB or 88% of the original size.
Potential reduce by 188.6 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. Fanta images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 66% of the original size.
Potential reduce by 933.2 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. Fanta.eu needs all CSS files to be minified and compressed as it can save up to 933.2 kB or 85% of the original size.
Number of requests can be reduced by 92 (74%)
125
33
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fanta. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 74 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
fanta.eu
158 ms
www.fanta.com
305 ms
www.fanta.com
90 ms
fontawesome.min.css
36 ms
dependencies.min.css
53 ms
bootstrap.min.css
54 ms
slick.min.css
43 ms
virtual-agent-css.min.css
51 ms
angular-ui.min.css
59 ms
code-entry.min.css
65 ms
alert.min.css
63 ms
code-scan.min.css
62 ms
keyboard-alphanumeric.min.css
64 ms
angular-ui-select.min.css
70 ms
donation.min.css
70 ms
mks-button.min.css
67 ms
brandscom-all.min.css
70 ms
footer-libs.min.css
80 ms
main.css
81 ms
iframe_api
119 ms
jquery.min.js
77 ms
angular.min.js
99 ms
angular-sanitize.min.js
120 ms
angular-cookies.min.js
121 ms
spin.min.js
59 ms
angular-spinner.min.js
73 ms
utility.min.js
94 ms
itemDetail.min.js
74 ms
main.min.js
94 ms
commons.min.js
112 ms
dependencies.min.js
113 ms
picturefill.min.js
112 ms
slick.min.js
113 ms
vending-config.min.js
111 ms
authentication-manager.min.js
112 ms
user-agent.min.js
130 ms
angular-utility.min.js
130 ms
module-init.min.js
132 ms
answer-result.min.js
127 ms
angular-ui.min.js
130 ms
Bootstrap.js
420 ms
gzm4krv.js
134 ms
underscore-min.js
105 ms
KO-janrain-modal-custom.css
124 ms
federateModal.css
118 ms
sign-in.min.js
110 ms
error.min.js
109 ms
fileReader.min.js
102 ms
imageOnLoad.min.js
96 ms
fileChange.min.js
96 ms
liquid-print.min.js
97 ms
flock-to-unlock.min.js
92 ms
social-share.min.js
91 ms
code-entry.min.js
93 ms
alert.min.js
92 ms
thank-you.min.js
92 ms
code-scan.min.js
93 ms
keyboard-alphanumeric.min.js
89 ms
keyboard-code.min.js
87 ms
typeahead-search.min.js
90 ms
angular-ui-select.min.js
89 ms
donation.min.js
83 ms
recaptcha.min.js
87 ms
birth-date.min.js
81 ms
contact-us.min.js
64 ms
focusOn.min.js
64 ms
pathfinder.min.js
63 ms
accountLinker.min.js
64 ms
brandscom-all.min.js
45 ms
bootstrap.min.js
44 ms
mcr-legacy.min.js
64 ms
janrain.js
44 ms
dependencies.min.js
44 ms
commons.min.js
60 ms
formValidation.min.js
75 ms
survey.min.js
76 ms
loginReg.min.js
75 ms
federateModal.min.js
73 ms
hero-legacy.min.js
112 ms
footer-libs.min.js
110 ms
webtrends.hm.js
238 ms
wtid.js
681 ms
gtm.js
238 ms
fanta
223 ms
purple%20background.png
85 ms
infobar_onsiteAction.png
84 ms
infobar_Code.png
84 ms
infobar_Instagram.png
85 ms
infobar_Twitter.png
83 ms
Fanta-logo.png
83 ms
coca-cola-company.png
90 ms
country-picker.png
91 ms
social-icon-facebook.png
90 ms
social-icon-youtube.png
90 ms
social-icon-twitter.png
89 ms
social-icon-gplus.png
88 ms
fanta-bmtof-hero.jpg
186 ms
country-navigator-map-gray-updated.png
148 ms
btn-closed.png
147 ms
btn-open.png
148 ms
www-widgetapi.js
78 ms
liquid-print.html
67 ms
start.html
156 ms
fanta
132 ms
2C2144_0_0.woff
22 ms
serverComponent.php
98 ms
analytics.js
149 ms
HmLQ6AwFE6c
96 ms
liquid-print-styles.html
20 ms
%7B%7B$ctrl.processing.spinnerImage%7D%7D
214 ms
%7B%7B$ctrl.wideButton.image%7D%7D
214 ms
%7B%7B$ctrl.smallButton.image%7D%7D
210 ms
scan_now_id.png
210 ms
ic_info_outline_black_24dp.png
209 ms
spinner-orange.gif
115 ms
liquidprint-coca-cola.png
210 ms
error.png
211 ms
5498a821538620bf12d449f8bdfd0fc7.js
204 ms
www-player-vflMqr8uC.css
73 ms
www-embed-player.js
72 ms
base.js
104 ms
12328561b0e8dcc3970de3a2ba9d21b8.js
294 ms
en-US
100 ms
complete.html
152 ms
collect
227 ms
id
150 ms
YubHWiCUdycrt9r0pwxtCFMvWBBxMHmgtw0lFaZzSbY.js
117 ms
ad_status.js
120 ms
watermark_ringo-vflPWbiPS.png
18 ms
capture:login
41 ms
105 ms
101 ms
sso.js
79 ms
providers.css
52 ms
17c96fc4b9c8464d1c95cd785dd3120b.png
37 ms
fanta.eu 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
button, link, and menuitem elements do not have accessible names.
[role]s are not contained by their required parent element
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
Some elements have a [tabindex] value greater than 0
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
fanta.eu 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
fanta.eu 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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fanta.eu 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 Fanta.eu 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.
fanta.eu
Open Graph data is detected on the main page of Fanta. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: