2.9 sec in total
40 ms
2.7 sec
178 ms
Welcome to iwantfrieswiththat.com homepage info - get ready to check Iwant Fries Withthat best content right away, or after learning these important things about iwantfrieswiththat.com
McDonalds.com is your hub for everything McDonald's. Find out more about our menu items and promotions today!
Visit iwantfrieswiththat.comWe analyzed Iwantfrieswiththat.com page load time and found that the first response time was 40 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
iwantfrieswiththat.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value22.3 s
0/100
25%
Value17.0 s
0/100
10%
Value21,910 ms
0/100
30%
Value0.134
80/100
15%
Value33.3 s
0/100
10%
40 ms
52 ms
22 ms
22 ms
24 ms
Our browser made a total of 204 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Iwantfrieswiththat.com, 9% (19 requests) were made to Assets.adobedtm.com and 4% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (721 ms) relates to the external source Embed.spotify.com.
Page size can be reduced by 1.0 MB (48%)
2.2 MB
1.1 MB
In fact, the total size of Iwantfrieswiththat.com main page is 2.2 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. 75% 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. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 98.7 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 14.9 kB, which is 13% 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 98.7 kB or 83% of the original size.
Potential reduce by 85.2 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, Iwant Fries Withthat needs image optimization as it can save up to 85.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 723.8 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 723.8 kB or 66% of the original size.
Potential reduce by 138.0 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. Iwantfrieswiththat.com needs all CSS files to be minified and compressed as it can save up to 138.0 kB or 82% of the original size.
Number of requests can be reduced by 114 (58%)
195
81
The browser has sent 195 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iwant Fries Withthat. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 66 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
home.html
40 ms
satelliteLib-545b802c4df58430a033a769202abcc2256a7f40.js
52 ms
McdAnalyticsEventsCapture.js
22 ms
mcdonalds.css
22 ms
food.css
24 ms
news.css
24 ms
contactus.css
23 ms
jquery.ui.theme.css
25 ms
jquery-1.3.2.min.js
64 ms
jquery.activetextinput.js
64 ms
global_utils.js
63 ms
jquery.mcdcolorbox.css
63 ms
jquery.colorbox-mod.js
62 ms
jquery.mcdcolorbox.js
45 ms
jquery.callouts.js
66 ms
jquery-ui-1.7.2.custom.min.js
66 ms
jquery.ifixpng.js
66 ms
commons.js
64 ms
datepicker.js
64 ms
custom-form-elements.js
63 ms
textArea.js
83 ms
formValidation.js
81 ms
page-grayed-out.js
82 ms
textresize.js
98 ms
news.js
95 ms
jquery_newsarticles.js
97 ms
DD_roundies_0.0.2a-min.js
101 ms
swfobject.js
101 ms
mealbuilder.js
101 ms
jquery.cookie.js
101 ms
mealbuilder.cookie.js
102 ms
jquery.min.1.7.js
108 ms
TweenMax.min.js
107 ms
foresee-trigger.js
109 ms
topnav_join.js
104 ms
topnav_join.css
106 ms
all.js
9 ms
platform.js
100 ms
id
31 ms
mbox-contents-035a728a3306a43ac17a9b43e8934b6522456c87.js
30 ms
analytics.js
12 ms
collect
31 ms
target.js
167 ms
id
14 ms
collect
54 ms
ajax
31 ms
css
55 ms
print.css
18 ms
logoimage.img.png
97 ms
1456346341228.jpg
96 ms
1452548202744.jpg
93 ms
1450826788167.jpg
101 ms
share_email.png
93 ms
share_facebook.png
93 ms
share_twitter.png
95 ms
share_delicious.png
105 ms
share_digg.png
106 ms
value2for5_logo.png
113 ms
value2for5_title0.png
115 ms
value2for5_title1.png
105 ms
value2for5_title2.png
106 ms
value2for5_title3.png
110 ms
value2for5_subtitle0.png
110 ms
value2for5_subtitle1.png
111 ms
value2for5_subtitle2.png
112 ms
value2for5_sublogo2.png
112 ms
value2for5_subtitle3.png
113 ms
value2for5_ctatitle.png
114 ms
value2for5_ctasubtitle.png
115 ms
value2for5_cta.png
115 ms
widgets.js
122 ms
721 ms
follow_button.html
92 ms
0.gif
49 ms
373 ms
xd_arbiter.php
64 ms
xd_arbiter.php
212 ms
platform.js
161 ms
ga.js
50 ms
satellite-55fdb48235306300170002bf.html
50 ms
satellite-55fdbae235396200140004cc.html
153 ms
satellite-55fdbc4e35306300170002c1.html
192 ms
satellite-55fdbc4e35306300170002c2.html
191 ms
satellite-5630130764746d2a4a0026b3.html
189 ms
satellite-5630130764746d2a4a0026b4.html
195 ms
satellite-5630130764746d2a4a0026b5.html
197 ms
tag.js
191 ms
satellite-55fdc641353962001700036c.html
201 ms
satellite-55fdc641353962001700036d.html
199 ms
satellite-55fdc641353962001700036e.html
198 ms
satellite-55fdc641353962001700036f.html
197 ms
satellite-563014df64746d7fa2002456.html
330 ms
satellite-563014df64746d7fa2002457.html
199 ms
satellite-563014df64746d7fa2002458.html
316 ms
satellite-56a7647464746d31e7002d00.js
236 ms
s-code-contents-a87e38cc94724b76c2991453d1538225c637bd58.js
323 ms
d93e757e1104.png
187 ms
follow_button.js
174 ms
342 ms
380 ms
lb
442 ms
__utm.gif
122 ms
fbds.js
59 ms
topbar.png
74 ms
ul_bg.png
70 ms
1420757835486.png
65 ms
food_flyout_bg.png
277 ms
1456347566745.png
65 ms
promotions_flyout_bg.png
68 ms
1454350618298.png
196 ms
our_story_2_flyout_top_bg.png
195 ms
1418413323472.png
196 ms
1418413998023.png
195 ms
input_flyout_bg.png
195 ms
1418413421445.png
276 ms
1418413276303.png
276 ms
1425031373294.png
275 ms
1418414136669.png
272 ms
1418414393827.png
275 ms
topbar_spacer.png
338 ms
share_alt_bg.png
339 ms
value2for5_bg.jpg
641 ms
explore_bg.png
336 ms
carrot.png
337 ms
callouts_dropshadow_bg.png
336 ms
oct.js
183 ms
cb=gapi.loaded_0
162 ms
cb=gapi.loaded_1
263 ms
subscribe_embed
413 ms
ActivityServer.bs
463 ms
ga.js
349 ms
analytics.js
320 ms
follow_button_sprite.png
221 ms
ActivityServer.bs
450 ms
cf5f02a7dec1.png
172 ms
tag
260 ms
207 ms
269 ms
_Incapsula_Resource
263 ms
satellite-56cf42e264746d4aef00039f.js
177 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
328 ms
food_flyout_bg.png
329 ms
promotions_flyout_bg.png
184 ms
nav_single_column_bg.png
183 ms
input_flyout_bg.png
192 ms
overlay_bg.png
211 ms
right_arrow.png
210 ms
left_arrow.png
217 ms
McD_Family_desktop_callout.jpg
217 ms
GMA_callout.jpg
291 ms
AAG_callout2.jpg
289 ms
joinpoplogo.jpg
322 ms
join_container_foot_bg.png
320 ms
foresee-surveydef.js
367 ms
adsct
360 ms
adsct
195 ms
s56975206653587
101 ms
77 ms
postmessageRelay
244 ms
segment
34 ms
sha256.js
156 ms
_Incapsula_Resource
119 ms
like.php
166 ms
www-subscribe-embed-vflTum1sJ.css
223 ms
www-subscribe-embed.js
267 ms
__utm.gif
116 ms
__utm.gif
146 ms
Pug
243 ms
appnexus
121 ms
style.689b19ea.css
213 ms
app.1d5c9c90.js
245 ms
ebAttribution.js
413 ms
like.php
158 ms
generic
74 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
89 ms
qeKvIRsJabD.js
215 ms
LVx-xkvaJ0b.png
209 ms
3193398744-postmessagerelay.js
191 ms
rpc:shindig_random.js
107 ms
foresee-dhtml.css
116 ms
cs
68 ms
www-hitchhiker-vflvB63an.png
88 ms
cb=gapi.loaded_0
75 ms
sprite@1.04aacdf1.png
65 ms
generic
48 ms
cs
74 ms
cb=gapi.loaded_0
64 ms
qeKvIRsJabD.js
60 ms
cb=gapi.loaded_2
4 ms
border_3.gif
11 ms
subscribe_embed
61 ms
spacer.gif
5 ms
border_3.gif
6 ms
bubbleSprite_3.png
9 ms
bubbleDropR_3.png
10 ms
bubbleDropB_3.png
11 ms
www-subscribe-embed-card-vflqARhQ4.css
5 ms
www-subscribe-embed-card.js
7 ms
jot.html
29 ms
yahoo.ashx
183 ms
pixel
34 ms
pixel
16 ms
adex.ashx
195 ms
1
54 ms
iwantfrieswiththat.com accessibility score
iwantfrieswiththat.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
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
iwantfrieswiththat.com 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
Tap targets are not sized appropriately
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iwantfrieswiththat.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Iwantfrieswiththat.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
iwantfrieswiththat.com
Open Graph description is not detected on the main page of Iwant Fries Withthat. 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: