Tools & Wizards About Us
17fifa.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

17fifa.com

非凡网 | 专业FIFA游戏资讯站

Page Load Speed

44.8 sec in total

First Response

2 sec

Resources Loaded

42.4 sec

Page Rendered

411 ms

17fifa.com screenshot

About Website

Visit 17fifa.com now to see the best up-to-date 17 Fifa content for China and also check out these interesting facts you probably never knew about 17fifa.com

中国最好的FIFA游戏资讯站

Visit 17fifa.com

Key Findings

We analyzed 17fifa.com page load time and found that the first response time was 2 sec and then it took 42.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 27 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

17fifa.com performance score

0

Network Requests Diagram

17fifa.com

2019 ms

reset.css

902 ms

style.css

2600 ms

modernizr-2.6.2.dev.js

13812 ms

jquery-1.9.1.min.js

19781 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 31% of them (38 requests) were addressed to the original 17fifa.com, 6% (8 requests) were made to Pagead2.googlesyndication.com and 6% (7 requests) were made to Img.t.sinajs.cn. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain 17fifa.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 499.1 kB (30%)

Content Size

1.6 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 34.9 kB

  • Original 43.3 kB
  • After minification 42.3 kB
  • After compression 8.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 34.9 kB or 80% of the original size.

Image Optimization

-13%

Potential reduce by 145.0 kB

  • Original 1.1 MB
  • After minification 935.3 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, 17 Fifa needs image optimization as it can save up to 145.0 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 190.8 kB

  • Original 356.6 kB
  • After minification 323.2 kB
  • After compression 165.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 190.8 kB or 53% of the original size.

CSS Optimization

-81%

Potential reduce by 128.5 kB

  • Original 159.0 kB
  • After minification 155.5 kB
  • After compression 30.6 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. 17fifa.com needs all CSS files to be minified and compressed as it can save up to 128.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (28%)

Requests Now

96

After Optimization

69

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

17fifa.com

17fifa.com

2019 ms

reset.css

reset.css

902 ms

style.css

style.css

2600 ms

modernizr-2.6.2.dev.js

modernizr-2.6.2.dev.js

13812 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

19781 ms

jquery.zaccordion.min.js

jquery.zaccordion.min.js

5851 ms

adsbygoogle.js

adsbygoogle.js

13 ms

show_ads.js

show_ads.js

3 ms

logo.png

logo.png

4100 ms

search-go.png

search-go.png

576 ms

nav-bg-current.png

nav-bg-current.png

574 ms

banner-160-100.png

banner-160-100.png

19993 ms

image.php

image.php

19992 ms

image.php

image.php

19993 ms

image.php

image.php

19993 ms

image.php

image.php

19659 ms

image.php

image.php

14605 ms

image.php

image.php

19290 ms

image.php

image.php

19992 ms

image.php

image.php

19993 ms

image.php

image.php

19993 ms

image.php

image.php

19993 ms

image.php

image.php

19993 ms

image.php

image.php

19992 ms

image.php

image.php

19993 ms

image.php

image.php

19992 ms

image.php

image.php

19993 ms

image.php

image.php

19992 ms

image.php

image.php

19992 ms

image.php

image.php

19992 ms

image.php

image.php

19991 ms

image.php

image.php

19989 ms

image.php

image.php

19989 ms

image.php

image.php

19988 ms

image.php

image.php

19989 ms

image.php

image.php

19988 ms

image.php

image.php

19988 ms

ea-gamescom.jpg

ea-gamescom.jpg

19989 ms

ca-pub-3129134624106167.js

ca-pub-3129134624106167.js

160 ms

zrt_lookup.html

zrt_lookup.html

85 ms

show_ads_impl.js

show_ads_impl.js

85 ms

tabs-bg.png

tabs-bg.png

19951 ms

tabs-bg-current.png

tabs-bg-current.png

19950 ms

index.php

index.php

1151 ms

embed.js

embed.js

574 ms

h.js

h.js

629 ms

ads

ads

234 ms

osd.js

osd.js

20 ms

ads

ads

194 ms

ads

ads

205 ms

1512374864664268028

1512374864664268028

61 ms

abg.js

abg.js

81 ms

m_js_controller.js

m_js_controller.js

71 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

54 ms

13852445234897023064

13852445234897023064

169 ms

2134566359562001662

2134566359562001662

140 ms

s

s

71 ms

x_button_blue2.png

x_button_blue2.png

30 ms

9aKOW9kHIBrJTB9ONj-e1oyTZuOGlgCE-J5p-KupNmo.js

9aKOW9kHIBrJTB9ONj-e1oyTZuOGlgCE-J5p-KupNmo.js

12 ms

embed.compat.js

embed.compat.js

168 ms

21.gif

21.gif

872 ms

hm.gif

hm.gif

414 ms

listRecentPosts.json

listRecentPosts.json

1282 ms

weiboShow.css

weiboShow.css

235 ms

skin05.css

skin05.css

233 ms

gaea_1_19.js

gaea_1_19.js

267 ms

show.js

show.js

233 ms

suda.js

suda.js

229 ms

1

1

89 ms

btns_bg.png

btns_bg.png

74 ms

70ab1f4fjw1f2pqq6n7vnj20qo0qodqb.jpg

70ab1f4fjw1f2pqq6n7vnj20qo0qodqb.jpg

497 ms

70ab1f4fjw1f2pqjusjb0j21kw11odr4.jpg

70ab1f4fjw1f2pqjusjb0j21kw11odr4.jpg

385 ms

70ab1f4fjw1f2pn4cs1jbj212w0g7dka.jpg

70ab1f4fjw1f2pn4cs1jbj212w0g7dka.jpg

223 ms

7a351cfdjw1f2jt8y7zo0j20t80loq74.jpg

7a351cfdjw1f2jt8y7zo0j20t80loq74.jpg

83 ms

1

1

912 ms

1

1

73 ms

1

1

284 ms

1

1

64 ms

1

1

60 ms

1

1

62 ms

1

1

287 ms

70ab1f4fjw1f2p9xuy9chj20i70q8gqj.jpg

70ab1f4fjw1f2p9xuy9chj20i70q8gqj.jpg

73 ms

70ab1f4fgw1f2ocjn7t6oj20sw12o452.jpg

70ab1f4fgw1f2ocjn7t6oj20sw12o452.jpg

59 ms

70ab1f4fjw1f2m6mf02r6j20nm0nh79p.jpg

70ab1f4fjw1f2m6mf02r6j20nm0nh79p.jpg

58 ms

70ab1f4fjw1f2jitujamuj20sg0sggwy.jpg

70ab1f4fjw1f2jitujamuj20sg0sggwy.jpg

70 ms

6de2d984gw1f2ics4b7msg20bn06kkjn.gif

6de2d984gw1f2ics4b7msg20bn06kkjn.gif

66 ms

bdbf05a0jw1f2i33ob0wqj20lc0lcwga.jpg

bdbf05a0jw1f2i33ob0wqj20lc0lcwga.jpg

91 ms

1

1

62 ms

1

1

63 ms

1

1

420 ms

1

1

72 ms

1

1

64 ms

1

1

868 ms

1

1

900 ms

1

1

893 ms

1

1

894 ms

1

1

255 ms

1

1

85 ms

0

0

69 ms

1

1

66 ms

icon_follow.png

icon_follow.png

50 ms

icon_user.png

icon_user.png

51 ms

70ab1f4fjw1f2kq18d1m7j20qc0qoah1.jpg

70ab1f4fjw1f2kq18d1m7j20qc0qoah1.jpg

69 ms

70ab1f4fjw1f2kokcziqqj20iz0nfq5m.jpg

70ab1f4fjw1f2kokcziqqj20iz0nfq5m.jpg

57 ms

70ab1f4fjw1f2k1uyqj96j21350m5am2.jpg

70ab1f4fjw1f2k1uyqj96j21350m5am2.jpg

82 ms

70ab1f4fjw1f2jk6ovs3dj20oy0mxdk2.jpg

70ab1f4fjw1f2jk6ovs3dj20oy0mxdk2.jpg

56 ms

70ab1f4fgw1f2o91gx6y4j20ls0nptdl.jpg

70ab1f4fgw1f2o91gx6y4j20ls0nptdl.jpg

61 ms

70ab1f4fjw1f2ncdz7hytj20h00h00vt.jpg

70ab1f4fjw1f2ncdz7hytj20h00h00vt.jpg

66 ms

bg_trans.png

bg_trans.png

38 ms

icon_tips.png

icon_tips.png

37 ms

a.gif

a.gif

985 ms

tmp.gif

tmp.gif

1081 ms

activeview

activeview

16 ms

activeview

activeview

30 ms

embed.bluebox.css

embed.bluebox.css

97 ms

50

50

18821 ms

100

100

15480 ms

180858.jpg

180858.jpg

1253 ms

1

1

34 ms

1

1

266 ms

50

50

18819 ms

100

100

15478 ms

100

100

15570 ms

100

100

15637 ms

SEO Factors

17fifa.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 17fifa.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that 17fifa.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

17fifa.com

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