Your Website Score is
SEO Rank : 14 Website URL: zhaofuli.in Last Updated: 5 months
Success
40% of passed verification steps
Warning
30% of total warning
Errors
30% of total errors, require fast action
Share
Estimation Traffic and Earnings
0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 0%
Domain Authority
Domain Authority 0%
Moz Rank
0.0/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
0 Characters
NO DATA
Meta Description
0 Characters
NO DATA
Effective URL
18 Characters
http://zhaofuli.in
Excerpt
Page content
紧急通知本站仅支持UC浏览器访问！用UC浏览器打开请使用手机浏览器扫码下载UC浏览器（暂不支持微信扫码访问）UC浏览器访问网站：没有广告电影播放不卡顿精彩视频存入网盘随时看
Google Preview
Your look like this in google search result
zhaofuli.in
http://zhaofuli.in
紧急通知本站仅支持UC浏览器访问！用UC浏览器打开请使用手机浏览器扫码下载UC浏览器（暂不支持微信扫码访问）UC浏览器访问网站：没有广告电影播放不卡顿精彩视频存入网盘随时看
Robots.txt
File Detected
Sitemap.xml
File Detected
Page Size
Code & Text Ratio
Document Size: ~3.47 KB
Code Size: ~2.13 KB
Text Size: ~1.34 KB Ratio: 38.53%
Social Data
Desktop
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Keep request counts low and transfer sizes small
8 requests • 25 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First CPU Idle
0.5 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Avoids enormous network payloads
Total size was 25 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize third-party usage
Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Largest Contentful Paint
0.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids an excessive DOM size
1 element
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Max Potential First Input Delay
20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Time to Interactive
0.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
robots.txt is not valid
1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Initial server response time was short
Root document took 40 ms
Keep the server response time for the main document short because all other requests depend on it
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minimizes main-thread work
0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Does not use HTTPS
3 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
First Meaningful Paint
0.5 s
First Meaningful Paint measures when the primary content of a page is visible
Estimated Input Latency
10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Uses efficient cache policy on static assets
0 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid chaining critical requests
4 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
First Contentful Paint
0.5 s
First Contentful Paint marks the time at which the first text or image is painted
Mobile
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Avoids an excessive DOM size
1 element
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Avoid long main-thread tasks
2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Speed Index
1.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Avoids enormous network payloads
Total size was 3 KiB
Large network payloads cost users real money and are highly correlated with long load times
Initial server response time was short
Root document took 80 ms
Keep the server response time for the main document short because all other requests depend on it
Minimize third-party usage
Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
First CPU Idle
1.5 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
JavaScript execution time
0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid chaining critical requests
4 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
First Contentful Paint (3G)
2925 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
First Meaningful Paint
1.5 s
First Meaningful Paint measures when the primary content of a page is visible
Minimizes main-thread work
0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive
1.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Max Potential First Input Delay
20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint
1.5 s
First Contentful Paint marks the time at which the first text or image is painted
robots.txt is not valid
1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Preload key requests
Potential savings of 180 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Largest Contentful Paint
1.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Does not use HTTPS
3 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Uses efficient cache policy on static assets
0 resources found
A long cache lifetime can speed up repeat visits to your page
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Keep request counts low and transfer sizes small
8 requests • 3 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Estimated Input Latency
10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Speed And Optimization Tips
Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Warning! Your title is not optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Warning! Your website is not SSL secured (HTTPS).
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links
View links
| First 0 Links | Relationship | HTTP Status |
Alexa Rank
0
Local Rank: / Users: / PageViews:
Global Rank
Domain Available
| Domain (TDL) and Typo | Status |
|---|---|
| zhaofuli.co | Available Buy Now! |
| zhaofuli.us | Available Buy Now! |
| zhaofuli.com | Already Registered |
| zhaofuli.org | Already Registered |
| zhaofuli.net | Already Registered |
| zaofuli.in | Available Buy Now! |
| ahaofuli.in | Available Buy Now! |
| whaofuli.in | Available Buy Now! |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Server: nginx
Date: Sun, 16 Aug 2020 09:54:37 GMT
Content-Type: text/html
Last-Modified: Fri, 07 Aug 2020 04:02:04 GMT
Vary: Accept-Encoding
ETag: W/"5f2cd23c-d15"
Content-Encoding: gzip
Via: 1.1 google
Transfer-Encoding: chunked
Click to Add/Show Comments