Tools & Wizards About Us
amorgames.com screenshot

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

amorgames.com

Free games - MAD.com

Page Load Speed

3.6 sec in total

First Response

189 ms

Resources Loaded

1.9 sec

Page Rendered

1.5 sec

amorgames.com screenshot

About Website

Click here to check amazing Amor Games content. Otherwise, check out these important facts you probably never knew about amorgames.com

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

Visit amorgames.com

Key Findings

We analyzed Amorgames.com page load time and found that the first response time was 189 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

amorgames.com performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value3.8 s

83/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

amorgames.com

189 ms

www.mad.com

96 ms

mad.com

178 ms

styles.css

25 ms

mad2.php

92 ms

Our browser made a total of 114 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Amorgames.com, 76% (87 requests) were made to Mad.ntnd.net and 7% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (693 ms) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 585.4 kB (22%)

Content Size

2.7 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Amorgames.com main page is 2.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. 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. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 171.3 kB

  • Original 197.8 kB
  • After minification 197.4 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 171.3 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 110.7 kB

  • Original 2.0 MB
  • After minification 1.9 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. Amor Games images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 294.5 kB

  • Original 489.0 kB
  • After minification 489.0 kB
  • After compression 194.5 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 294.5 kB or 60% of the original size.

CSS Optimization

-75%

Potential reduce by 8.8 kB

  • Original 11.8 kB
  • After minification 11.7 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. Amorgames.com needs all CSS files to be minified and compressed as it can save up to 8.8 kB or 75% of the original size.

Requests Breakdown

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

Requests Now

108

After Optimization

95

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

amorgames.com

amorgames.com

189 ms

www.mad.com

www.mad.com

96 ms

mad.com

mad.com

178 ms

styles.css

styles.css

25 ms

mad2.php

mad2.php

92 ms

sky.png

sky.png

4 ms

all.js

all.js

208 ms

jquery.min.js

jquery.min.js

28 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

3 ms

index.min.js

index.min.js

6 ms

mad2.php

mad2.php

91 ms

mountains.png

mountains.png

59 ms

plusone.js

plusone.js

681 ms

logo.png

logo.png

21 ms

search.png

search.png

20 ms

searchButton.png

searchButton.png

60 ms

search-top.png

search-top.png

61 ms

dropdownSelected.png

dropdownSelected.png

58 ms

flags.png

flags.png

59 ms

downArrow.png

downArrow.png

59 ms

dropdown-top.png

dropdown-top.png

482 ms

grass.png

grass.png

481 ms

dimmer.png

dimmer.png

481 ms

flyoutBack.png

flyoutBack.png

466 ms

sheep.png

sheep.png

450 ms

burbin_casual_nc-webfont.woff

burbin_casual_nc-webfont.woff

466 ms

693 ms

analytics.js

analytics.js

221 ms

1.jpg

1.jpg

169 ms

2.jpg

2.jpg

168 ms

3.jpg

3.jpg

172 ms

4.jpg

4.jpg

172 ms

5.jpg

5.jpg

171 ms

6.jpg

6.jpg

170 ms

7.jpg

7.jpg

172 ms

8.jpg

8.jpg

184 ms

9.jpg

9.jpg

174 ms

10.jpg

10.jpg

184 ms

11.jpg

11.jpg

172 ms

12.jpg

12.jpg

184 ms

13.jpg

13.jpg

186 ms

14.jpg

14.jpg

188 ms

15.jpg

15.jpg

176 ms

16.jpg

16.jpg

177 ms

17.jpg

17.jpg

199 ms

18.jpg

18.jpg

179 ms

19.jpg

19.jpg

180 ms

20.jpg

20.jpg

180 ms

21.jpg

21.jpg

181 ms

22.jpg

22.jpg

194 ms

23.jpg

23.jpg

195 ms

24.jpg

24.jpg

197 ms

25.jpg

25.jpg

199 ms

26.jpg

26.jpg

198 ms

27.jpg

27.jpg

200 ms

28.jpg

28.jpg

199 ms

29.jpg

29.jpg

203 ms

30.jpg

30.jpg

202 ms

31.jpg

31.jpg

201 ms

32.jpg

32.jpg

202 ms

33.jpg

33.jpg

221 ms

34.jpg

34.jpg

221 ms

35.jpg

35.jpg

230 ms

fTmIQU3LxvB.js

fTmIQU3LxvB.js

203 ms

fTmIQU3LxvB.js

fTmIQU3LxvB.js

401 ms

36.jpg

36.jpg

155 ms

37.jpg

37.jpg

155 ms

38.jpg

38.jpg

153 ms

39.jpg

39.jpg

153 ms

40.jpg

40.jpg

152 ms

41.jpg

41.jpg

153 ms

42.jpg

42.jpg

155 ms

43.jpg

43.jpg

152 ms

44.jpg

44.jpg

151 ms

45.jpg

45.jpg

144 ms

46.jpg

46.jpg

139 ms

47.jpg

47.jpg

141 ms

48.jpg

48.jpg

142 ms

49.jpg

49.jpg

152 ms

50.jpg

50.jpg

152 ms

51.jpg

51.jpg

149 ms

52.jpg

52.jpg

140 ms

53.jpg

53.jpg

148 ms

54.jpg

54.jpg

153 ms

55.jpg

55.jpg

136 ms

56.jpg

56.jpg

135 ms

57.jpg

57.jpg

137 ms

58.jpg

58.jpg

133 ms

59.jpg

59.jpg

134 ms

60.jpg

60.jpg

135 ms

moshi_monsters.jpg

moshi_monsters.jpg

144 ms

minion_rush.jpg

minion_rush.jpg

142 ms

cs_portable.jpg

cs_portable.jpg

142 ms

pokemon_tower_defense.jpg

pokemon_tower_defense.jpg

142 ms

bad_piggies_2.jpg

bad_piggies_2.jpg

141 ms

talking_tom_cat_2.jpg

talking_tom_cat_2.jpg

157 ms

thumbnailBorder.png

thumbnailBorder.png

156 ms

thumbnailBorderX4.png

thumbnailBorderX4.png

137 ms

modalBackground.png

modalBackground.png

136 ms

like.php

like.php

245 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

71 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

117 ms

fastbutton

fastbutton

218 ms

collect

collect

162 ms

postmessageRelay

postmessageRelay

136 ms

2OG98V2ZrtL.js

2OG98V2ZrtL.js

326 ms

FEppCFCt76d.png

FEppCFCt76d.png

356 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

38 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

36 ms

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

76 ms

ga-audiences

ga-audiences

111 ms

1240234406-postmessagerelay.js

1240234406-postmessagerelay.js

42 ms

rpc:shindig_random.js

rpc:shindig_random.js

38 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

11 ms

Accessibility Review

amorgames.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

amorgames.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

amorgames.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 Amorgames.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 Amorgames.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

amorgames.com

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