Tools & Wizards About Us
f166.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

f166.com

f166手游网_为您提供最好的手游下载门户

Page Load Speed

19.7 sec in total

First Response

1.9 sec

Resources Loaded

16.5 sec

Page Rendered

1.2 sec

f166.com screenshot

About Website

Click here to check amazing F 166 content. Otherwise, check out these important facts you probably never knew about f166.com

f166手游网为您提供最新最好玩的安卓手游下载，常用的Android应用软件下载，每日不断更新资讯、攻略，为您带来最好的体验，f166手游网全力打造互联网精品游戏软件下载基地。

Visit f166.com

Key Findings

We analyzed F166.com page load time and found that the first response time was 1.9 sec and then it took 17.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

f166.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value17.5 s

0/100

10%

TBT (Total Blocking Time)

Value2,700 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.193

64/100

15%

TTI (Time to Interactive)

Value20.7 s

2/100

10%

Network Requests Diagram

f166.com

1912 ms

f166skin.css

1005 ms

index.css

1024 ms

global.css

1889 ms

main.css

1113 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 73% of them (67 requests) were addressed to the original F166.com, 12% (11 requests) were made to Api.map.baidu.com and 5% (5 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (7 sec) relates to the external source Js.users.51.la.

Page Optimization Overview & Recommendations

Page size can be reduced by 287.4 kB (21%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 69.6 kB

  • Original 89.1 kB
  • After minification 82.1 kB
  • After compression 19.4 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 69.6 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 48.7 kB

  • Original 1.0 MB
  • After minification 982.4 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. F 166 images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 123.4 kB

  • Original 192.9 kB
  • After minification 185.1 kB
  • After compression 69.6 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 123.4 kB or 64% of the original size.

CSS Optimization

-76%

Potential reduce by 45.7 kB

  • Original 60.0 kB
  • After minification 46.9 kB
  • After compression 14.3 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. F166.com needs all CSS files to be minified and compressed as it can save up to 45.7 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (39%)

Requests Now

90

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of F 166. 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 from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

f166.com

f166.com

1912 ms

f166skin.css

f166skin.css

1005 ms

index.css

index.css

1024 ms

global.css

global.css

1889 ms

main.css

main.css

1113 ms

jquery1.8.js

jquery1.8.js

1972 ms

lhgcore.min.js

lhgcore.min.js

1528 ms

lhgdialog.min.js

lhgdialog.min.js

1325 ms

global.js

global.js

1593 ms

index.js

index.js

1387 ms

8062753.js

8062753.js

7038 ms

api

api

790 ms

themesJS.js

themesJS.js

573 ms

default.css

default.css

252 ms

037.gif

037.gif

2159 ms

038.gif

038.gif

2167 ms

topad1.jpg

topad1.jpg

654 ms

logo.gif

logo.gif

308 ms

taiguo.jpg

taiguo.jpg

1679 ms

hanguo.jpg

hanguo.jpg

903 ms

riben.jpg

riben.jpg

4369 ms

meiguo.jpg

meiguo.jpg

2920 ms

gangao.jpg

gangao.jpg

4653 ms

zhangjiajie.jpg

zhangjiajie.jpg

1445 ms

qianzheng.jpg

qianzheng.jpg

1443 ms

songgangao.gif

songgangao.gif

1723 ms

ReadImage.aspx

ReadImage.aspx

1698 ms

ReadImage.aspx

ReadImage.aspx

1929 ms

ReadImage.aspx

ReadImage.aspx

2194 ms

ReadImage.aspx

ReadImage.aspx

1987 ms

searchdata.gif

searchdata.gif

2194 ms

riben.jpg

riben.jpg

2793 ms

meiguo.jpg

meiguo.jpg

2470 ms

gangao.jpg

gangao.jpg

2479 ms

ouzhou.jpg

ouzhou.jpg

2996 ms

pujidao.jpg

pujidao.jpg

2752 ms

balidao.jpg

balidao.jpg

3026 ms

hainan.jpg

hainan.jpg

3089 ms

yunnan.jpg

yunnan.jpg

3264 ms

xiamen.jpg

xiamen.jpg

3282 ms

huadong.jpg

huadong.jpg

3282 ms

beijingshuangfei.jpg

beijingshuangfei.jpg

3360 ms

xian.jpg

xian.jpg

3872 ms

jiameng.jpg

jiameng.jpg

3597 ms

dandong.jpg

dandong.jpg

3844 ms

panjin.jpg

panjin.jpg

3904 ms

anben.jpg

anben.jpg

4399 ms

div_cloase.png

div_cloase.png

4091 ms

headerbg2.gif

headerbg2.gif

4110 ms

side1.gif

side1.gif

4132 ms

menubg.gif

menubg.gif

4314 ms

side2.gif

side2.gif

4384 ms

home_sprite.png

home_sprite.png

4115 ms

preload.gif

preload.gif

3951 ms

arrow3.gif

arrow3.gif

3746 ms

no_bg.gif

no_bg.gif

3211 ms

help1.gif

help1.gif

3224 ms

ico1.gif

ico1.gif

3004 ms

help2.gif

help2.gif

3183 ms

help3.gif

help3.gif

3256 ms

help4.gif

help4.gif

3052 ms

side4.gif

side4.gif

2935 ms

icon_12.gif

icon_12.gif

550 ms

shell_v2.js

shell_v2.js

477 ms

qq_back.png

qq_back.png

254 ms

qq_hid.jpg

qq_hid.jpg

311 ms

qq_dis.jpg

qq_dis.jpg

273 ms

getscript

getscript

1125 ms

bmap.css

bmap.css

503 ms

bds_s_v2.js

bds_s_v2.js

518 ms

bdsstyle.css

bdsstyle.css

254 ms

l0.gif

l0.gif

503 ms

3050 ms

copyright_logo.png

copyright_logo.png

282 ms

visa.asp

visa.asp

1858 ms

logger.js

logger.js

295 ms

blank.gif

blank.gif

625 ms

getmodules

getmodules

502 ms

lhgdg_bg.png

lhgdg_bg.png

270 ms

lhgdg_x.png

lhgdg_x.png

280 ms

wait.gif

wait.gif

256 ms

us_mk_icon.png

us_mk_icon.png

571 ms

iws3.png

iws3.png

299 ms

iw3.png

iw3.png

296 ms

iw_close.gif

iw_close.gif

404 ms

iw_plus.gif

iw_plus.gif

513 ms

blank.gif

blank.gif

431 ms

div_cloase.png

div_cloase.png

581 ms

navi_back.gif

navi_back.gif

261 ms

button_121.gif

button_121.gif

457 ms

button_121.gif

button_121.gif

466 ms

button_121.gif

button_121.gif

630 ms

Accessibility Review

f166.com accessibility score

78

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

f166.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

f166.com SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise F166.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 F166.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

f166.com

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