Tools & Wizards About Us
mad.com screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

mad.com

Free games - MAD.com

Page Load Speed

2.5 sec in total

First Response

109 ms

Resources Loaded

1.6 sec

Page Rendered

704 ms

mad.com screenshot

About Website

Welcome to mad.com homepage info - get ready to check MAD best content for United States right away, or after learning these important things about mad.com

Free games like fighting games, racing games, dressup games, and shooting games!

Visit mad.com

Key Findings

We analyzed Mad.com page load time and found that the first response time was 109 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

mad.com performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

mad.com

109 ms

mad.com

190 ms

styles.css

204 ms

mad2.php

225 ms

all.js

24 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Mad.com, 81% (88 requests) were made to Mad.ntnd.net and 6% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (453 ms) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 357.9 kB (15%)

Content Size

2.4 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mad.com main page is 2.4 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. 70% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 172.5 kB

  • Original 199.0 kB
  • After minification 198.6 kB
  • After compression 26.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. 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 172.5 kB or 87% of the original size.

Image Optimization

-9%

Potential reduce by 184.8 kB

  • Original 2.0 MB
  • After minification 1.8 MB

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. MAD images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 569 B

  • Original 213.9 kB
  • After minification 213.9 kB
  • After compression 213.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 14 B

  • Original 3.0 kB
  • After minification 3.0 kB
  • After compression 3.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. Mad.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (12%)

Requests Now

103

After Optimization

91

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MAD. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

mad.com

mad.com

109 ms

mad.com

mad.com

190 ms

styles.css

styles.css

204 ms

mad2.php

mad2.php

225 ms

all.js

all.js

24 ms

jquery.min.js

jquery.min.js

31 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

182 ms

index.min.js

index.min.js

193 ms

sky.png

sky.png

62 ms

mad2.php

mad2.php

159 ms

mountains.png

mountains.png

40 ms

logo.png

logo.png

226 ms

search.png

search.png

226 ms

searchButton.png

searchButton.png

225 ms

search-top.png

search-top.png

256 ms

dropdownSelected.png

dropdownSelected.png

256 ms

flags.png

flags.png

257 ms

downArrow.png

downArrow.png

309 ms

dropdown-top.png

dropdown-top.png

307 ms

grass.png

grass.png

312 ms

dimmer.png

dimmer.png

308 ms

flyoutBack.png

flyoutBack.png

311 ms

sheep.png

sheep.png

332 ms

plusone.js

plusone.js

216 ms

all.js

all.js

14 ms

burbin_casual_nc-webfont.woff

burbin_casual_nc-webfont.woff

309 ms

analytics.js

analytics.js

80 ms

1.jpg

1.jpg

137 ms

2.jpg

2.jpg

115 ms

3.jpg

3.jpg

136 ms

4.jpg

4.jpg

164 ms

5.jpg

5.jpg

138 ms

6.jpg

6.jpg

139 ms

7.jpg

7.jpg

281 ms

8.jpg

8.jpg

288 ms

9.jpg

9.jpg

287 ms

10.jpg

10.jpg

286 ms

11.jpg

11.jpg

286 ms

12.jpg

12.jpg

325 ms

13.jpg

13.jpg

327 ms

14.jpg

14.jpg

326 ms

15.jpg

15.jpg

329 ms

16.jpg

16.jpg

328 ms

17.jpg

17.jpg

355 ms

18.jpg

18.jpg

354 ms

19.jpg

19.jpg

356 ms

20.jpg

20.jpg

356 ms

21.jpg

21.jpg

357 ms

22.jpg

22.jpg

391 ms

23.jpg

23.jpg

391 ms

24.jpg

24.jpg

391 ms

25.jpg

25.jpg

391 ms

26.jpg

26.jpg

390 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

42 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

67 ms

fastbutton

fastbutton

60 ms

27.jpg

27.jpg

394 ms

28.jpg

28.jpg

395 ms

29.jpg

29.jpg

396 ms

collect

collect

34 ms

30.jpg

30.jpg

346 ms

31.jpg

31.jpg

345 ms

32.jpg

32.jpg

376 ms

33.jpg

33.jpg

375 ms

collect

collect

53 ms

js

js

71 ms

34.jpg

34.jpg

375 ms

postmessageRelay

postmessageRelay

182 ms

35.jpg

35.jpg

358 ms

36.jpg

36.jpg

357 ms

37.jpg

37.jpg

371 ms

38.jpg

38.jpg

368 ms

39.jpg

39.jpg

371 ms

40.jpg

40.jpg

370 ms

41.jpg

41.jpg

368 ms

ga-audiences

ga-audiences

154 ms

developers.google.com

developers.google.com

453 ms

42.jpg

42.jpg

374 ms

43.jpg

43.jpg

257 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

19 ms

rpc:shindig_random.js

rpc:shindig_random.js

12 ms

44.jpg

44.jpg

255 ms

45.jpg

45.jpg

258 ms

46.jpg

46.jpg

257 ms

47.jpg

47.jpg

286 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

48.jpg

48.jpg

248 ms

49.jpg

49.jpg

247 ms

50.jpg

50.jpg

251 ms

51.jpg

51.jpg

250 ms

52.jpg

52.jpg

281 ms

53.jpg

53.jpg

252 ms

54.jpg

54.jpg

254 ms

55.jpg

55.jpg

256 ms

56.jpg

56.jpg

256 ms

57.jpg

57.jpg

281 ms

58.jpg

58.jpg

253 ms

59.jpg

59.jpg

254 ms

60.jpg

60.jpg

252 ms

dl_ad_174x174_A.gif

dl_ad_174x174_A.gif

313 ms

duck_life_space.jpg

duck_life_space.jpg

276 ms

duck_life_adventure.jpg

duck_life_adventure.jpg

253 ms

duck_life_battle.jpg

duck_life_battle.jpg

251 ms

duck_life_treasure_hunt.jpg

duck_life_treasure_hunt.jpg

248 ms

duck_life.jpg

duck_life.jpg

271 ms

duck_life_4.jpg

duck_life_4.jpg

280 ms

thumbnailBorder.png

thumbnailBorder.png

247 ms

thumbnailBorderX4.png

thumbnailBorderX4.png

247 ms

modalBackground.png

modalBackground.png

269 ms

Accessibility Review

mad.com accessibility score

54

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

mad.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

mad.com SEO score

54

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mad.com 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 Mad.com 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.

Social Sharing Optimization

mad.com

Open Graph description is not detected on the main page of MAD. 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: