f02.cn website information.

f02.cn domain name is registered by .CN top-level domain registry. See the other sites registred in .CN domain zone.

No name server records were found.

According to Alexa traffic rank the highest website f02.cn position was 43013 (in the world). The lowest Alexa rank position was 956291. Current position of f02.cn in Alexa rank database is below 1 million.

Website f02.cn Desktop speed measurement score (85/100) is better than the results of 80% of other sites and shows that the page is performing great on desktop computers.

f02.cn Mobile usability score (57/100) is better than the results of 1.03% of other sites and shows that the page mobile usability is poor and can be improved.

Mobile speed measurement score of f02.cn (63/100) is better than the results of 61.76% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

Date	Rank	Change
Apr-26-2024	N/A	N/A
Apr-25-2024	N/A	N/A
Apr-24-2024	N/A	N/A
Apr-23-2024	N/A	N/A
Apr-22-2024	N/A	N/A
Apr-21-2024	N/A	N/A
Apr-20-2024	N/A	N/A

f02.cn Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.

f02.cn whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.

f02.cn server information

Servers Location

IP Address

Country

Region

City

f02.cn desktop page speed rank

Last tested: 2018-10-27

Desktop Speed Good

85/100

f02.cn Desktop Speed Test Quick Summary

priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://www.f02.cn/web/css/jquery-1.9.1.min.js
http://www.f02.cn/web/js/control.js
http://www.f02.cn/web/js/login.js
http://qzonestyle.gtimg.cn/qzone/openapi/qc_loader.js
http://qzonestyle.gtimg.cn/qzone/openapi/qc-1.0.1.js

Optimize CSS Delivery of the following:

http://www.f02.cn/web/css/main.css
http://www.f02.cn/web/css/common.css

priority - 3 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://graph.qq.com/jsdkproxy/qc-1.0.1.js (expiration not specified)
http://qzonestyle.gtimg.cn/qzone/openapi/qc-1.0.1.js (10 minutes)
http://qzonestyle.gtimg.cn/qzone/openapi/qc_loader.js (10 minutes)
http://www.f02.cn/web/css/common.css (3 days)
http://www.f02.cn/web/css/index.js (3 days)
http://www.f02.cn/web/css/jquery-1.9.1.min.js (3 days)
http://www.f02.cn/web/css/main.css (3 days)
http://www.f02.cn/web/js/control.js (3 days)
http://www.f02.cn/web/js/login.js (3 days)

priority - 2 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 21.2KiB (7% reduction).

Losslessly compressing http://www.f02.cn/web/images/login_people_bg.png could save 2.1KiB (35% reduction).
Losslessly compressing http://qzonestyle.gtimg.cn/qzone/vas/opensns/res/img/Connect_logo_3.png could save 1.5KiB (42% reduction).
Losslessly compressing http://www.f02.cn/web/images/icon03.png could save 1.5KiB (62% reduction).
Losslessly compressing http://www.f02.cn/web/images/icon01.png could save 1,002B (67% reduction).
Losslessly compressing http://www.f02.cn/web/images/login_bg.png could save 946B (34% reduction).
Losslessly compressing http://www.f02.cn/web/images/banner01.jpg could save 935B (2% reduction).
Losslessly compressing http://www.f02.cn/web/images/banner03.jpg could save 935B (2% reduction).
Losslessly compressing http://www.f02.cn/web/images/banner02.jpg could save 921B (2% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_011.jpg could save 918B (11% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_044.jpg could save 911B (12% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_02.jpg could save 909B (17% reduction).
Losslessly compressing http://www.f02.cn/web/images/icon_02.jpg could save 908B (73% reduction).
Losslessly compressing http://www.f02.cn/web/images/icon_08.jpg could save 908B (60% reduction).
Losslessly compressing http://www.f02.cn/web/images/icon_09.jpg could save 908B (62% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_01.jpg could save 908B (17% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_03.jpg could save 908B (15% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_022.jpg could save 907B (11% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_033.jpg could save 905B (10% reduction).
Losslessly compressing http://www.f02.cn/web/images/logo.jpg could save 904B (20% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_04.jpg could save 904B (18% reduction).
Losslessly compressing http://www.f02.cn/web/images/people_01.png could save 896B (10% reduction).

priority - 2 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 16.2KiB (61% reduction).

Compressing https://graph.qq.com/jsdkproxy/qc-1.0.1.js could save 16.2KiB (61% reduction).

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 3.6KiB (23% reduction).

Minifying http://www.f02.cn/web/css/index.js could save 1.7KiB (22% reduction) after compression.
Minifying http://www.f02.cn/web/js/login.js could save 1.1KiB (29% reduction) after compression.
Minifying http://www.f02.cn/web/js/control.js could save 830B (19% reduction) after compression.

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 716B (14% reduction).

Minifying http://www.f02.cn/ could save 716B (14% reduction) after compression.

f02.cn Desktop Resources

Total Resources	43
Number of Hosts	9
Static Resources	30
JavaScript Resources	9
CSS Resources	2

f02.cn Desktop Resource Breakdown

f02.cn mobile page speed rank

Last tested: 2018-10-27

Mobile Speed Bad

63/100

f02.cn Mobile Speed Test Quick Summary

priority - 32 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

http://www.f02.cn/web/css/main.css
http://www.f02.cn/web/css/common.css

priority - 19 Reduce server response time

In our test, your server responded in 1.4 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 5 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 2 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 20.3KiB (7% reduction).

Losslessly compressing http://www.f02.cn/web/images/login_people_bg.png could save 2.1KiB (35% reduction).
Losslessly compressing http://qzonestyle.gtimg.cn/qzone/vas/opensns/res/img/Connect_logo_3.png could save 1.5KiB (42% reduction).
Losslessly compressing http://www.f02.cn/web/images/icon03.png could save 1.5KiB (62% reduction).
Losslessly compressing http://www.f02.cn/web/images/icon01.png could save 1,002B (67% reduction).
Losslessly compressing http://www.f02.cn/web/images/login_bg.png could save 946B (34% reduction).
Losslessly compressing http://www.f02.cn/web/images/banner01.jpg could save 935B (2% reduction).
Losslessly compressing http://www.f02.cn/web/images/banner03.jpg could save 935B (2% reduction).
Losslessly compressing http://www.f02.cn/web/images/banner02.jpg could save 921B (2% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_011.jpg could save 918B (11% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_044.jpg could save 911B (12% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_02.jpg could save 909B (17% reduction).
Losslessly compressing http://www.f02.cn/web/images/icon_02.jpg could save 908B (73% reduction).
Losslessly compressing http://www.f02.cn/web/images/icon_09.jpg could save 908B (62% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_01.jpg could save 908B (17% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_03.jpg could save 908B (15% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_022.jpg could save 907B (11% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_033.jpg could save 905B (10% reduction).
Losslessly compressing http://www.f02.cn/web/images/logo.jpg could save 904B (20% reduction).
Losslessly compressing http://www.f02.cn/web/images/pic_04.jpg could save 904B (18% reduction).
Losslessly compressing http://www.f02.cn/web/images/people_01.png could save 896B (10% reduction).

priority - 2 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 16.2KiB (61% reduction).

Compressing https://graph.qq.com/jsdkproxy/qc-1.0.1.js could save 16.2KiB (61% reduction).

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 3.6KiB (23% reduction).

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 716B (14% reduction).

Minifying http://www.f02.cn/ could save 716B (14% reduction) after compression.

f02.cn Mobile Resources

Total Resources	42
Number of Hosts	9
Static Resources	29
JavaScript Resources	9
CSS Resources	2

f02.cn Mobile Resource Breakdown

f02.cn mobile page usability

Last tested: 2018-10-27

Mobile Usability Bad

57/100

f02.cn Mobile Usability Test Quick Summary

priority - 38 Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

爱码客户端下载 and 5 others render only 5 pixels tall (16 CSS pixels).

| and 4 others render only 5 pixels tall (16 CSS pixels).

用户登录 renders only 5 pixels tall (16 CSS pixels).

找回密码 renders only 3 pixels tall (12 CSS pixels).
激活账号 renders only 3 pixels tall (12 CSS pixels).

下次自动登录 renders only 3 pixels tall (12 CSS pixels).

还不是会员， renders only 3 pixels tall (12 CSS pixels).

立即注册 renders only 4 pixels tall (14 CSS pixels).
只需一步，快速开始 renders only 3 pixels tall (12 CSS pixels).

云端远程接收验证码平台API集成、推广者享受分成 and 10 others render only 4 pixels tall (14 CSS pixels).

爱码平台介绍 and 3 others render only 6 pixels tall (20 CSS pixels).

/INTRODUCE and 3 others render only 5 pixels tall (16 CSS pixels).

+more renders only 3 pixels tall (12 CSS pixels).

爱码，国内首家可收发短信验证…的数月时间里会员量破三十万。 and 2 others render only 4 pixels tall (14 CSS pixels).

在线客服: renders only 4 pixels tall (14 CSS pixels).

爱码官方Q群: renders only 4 pixels tall (14 CSS pixels).

① 150520184（满） and 3 others render only 4 pixels tall (14 CSS pixels).

爱码验证码平台API and 9 others render only 4 pixels tall (14 CSS pixels).

priority - 28 Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,200 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <a href="http://bbs.zhu…display&fid=57">帮助中心</a> falls outside the viewport.
The element <a href="web/api.html">API接口</a> falls outside the viewport.
The element <a href="web/integral.html">积分说明</a> falls outside the viewport.
The element <li class="logintit">用户登录</li> falls outside the viewport.
The element <input id="userID" type="text" class="login-namebox"> falls outside the viewport.
The element <input id="password" type="text" name="password" class="login-passbox"> falls outside the viewport.
The element <a href="web/login_password.html">找回密码</a> falls outside the viewport.
The element <a href="web/activation.html">激活账号</a> falls outside the viewport.
The element <input type="button" class="but button-pink"> falls outside the viewport.
The element <a href="web/register.html">立即注册</a> falls outside the viewport.
The element <img src="http://qzonest…ect_logo_3.png"> falls outside the viewport.
The element <span>只需一步，快速开始</span> falls outside the viewport.
The element <a href="http://www.f02.cn/"> falls outside the viewport.
The element <ul>123</ul> falls outside the viewport.
The element <img id="Image6" src="web/images/pic_04.jpg"> falls outside the viewport.
The element <a href="web/product.html#aima04">开发者软件集成对接爱码API无条件可获得消费额10%分成</a> falls outside the viewport.
The element <span>/HOT LINE</span> falls outside the viewport.
The element <img src="web/images/icon03.png"> falls outside the viewport.
The element <strong>97372136</strong> falls outside the viewport.
The element <li class="online">爱码官方Q群:</li> falls outside the viewport.
The element <em>② 332350658（满）</em> falls outside the viewport.
The element <em>④ 42655400</em> falls outside the viewport.
The element <li class="link_tit">友情链接/LINK</li> falls outside the viewport.
The element <li>爱码平台吾爱破…口说明分类目录</li> falls outside the viewport.
The element <p>©Copyright 201…CP备09032741号-7</p> falls outside the viewport.

priority - 10 Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

priority - 4 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="index.html"></a> is close to 1 other tap targets.

The tap target <a href="index.html">首页</a> and 5 others are close to other tap targets.

The tap target <input id="userID" type="text" class="login-namebox"> is close to 1 other tap targets.

The tap target <input id="password" type="text" name="password" class="login-passbox"> is close to 2 other tap targets.

The tap target <a href="web/login_password.html">找回密码</a> is close to 2 other tap targets.
The tap target <a href="web/activation.html">激活账号</a> is close to 2 other tap targets.

The tap target <input id="autoLogin" type="checkbox" name="autoLogin"> is close to 2 other tap targets.

The tap target <input type="button" class="but button-pink"> is close to 2 other tap targets.

The tap target <a href="web/register.html">立即注册</a> is close to 2 other tap targets.

The tap target <li class="">1</li> and 1 others are close to other tap targets.

The tap target <li class="on">2</li> is close to 1 other tap targets.

f02.cn similar domains

Similar domains:

www.f02.com
www.f02.net
www.f02.org
www.f02.info
www.f02.biz
www.f02.us
www.f02.mobi
www.02.cn
www.f02.cn
www.c02.cn
www.fc02.cn
www.cf02.cn
www.d02.cn
www.fd02.cn
www.df02.cn
www.r02.cn
www.fr02.cn
www.rf02.cn
www.t02.cn
www.ft02.cn
www.tf02.cn
www.g02.cn
www.fg02.cn
www.gf02.cn
www.v02.cn
www.fv02.cn
www.vf02.cn
www.f2.cn
www.f0.cn

f02.cn Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.

f02.cn TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.

F02.CN 爱码手机验证码短信接收平台官网—手机验证码接收系统

f02.cn website information.

Weekly Rank Report

Advertisement

f02.cn Rank History

f02.cn whois

f02.cn server information

Servers Location

f02.cn desktop page speed rank

f02.cn Desktop Speed Test Quick Summary

priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 3 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 2 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 21.2KiB (7% reduction).

priority - 2 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 16.2KiB (61% reduction).

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 3.6KiB (23% reduction).

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 716B (14% reduction).

f02.cn Desktop Resources

f02.cn Desktop Resource Breakdown

f02.cn mobile page speed rank

f02.cn Mobile Speed Test Quick Summary

priority - 32 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 19 Reduce server response time

In our test, your server responded in 1.4 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 5 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 2 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 20.3KiB (7% reduction).

priority - 2 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 16.2KiB (61% reduction).

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 3.6KiB (23% reduction).

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 716B (14% reduction).

f02.cn Mobile Resources

f02.cn Mobile Resource Breakdown

f02.cn mobile page usability

f02.cn Mobile Usability Test Quick Summary

priority - 38 Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

priority - 28 Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,200 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

priority - 10 Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

priority - 4 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

f02.cn similar domains

f02.cn Ping

f02.cn TRACEROUTE