Your Website Score is

Similar Ranking

2
質問・疑問に答えるQ&AサイトOKWAVE
okwave.jp
2
МУЖСКОЙ ЖУРНАЛ MAXIM ONLINE. ОФИЦИАЛЬНЫЙ САЙТ ЛУЧШЕГО МУЖСКОГО ЖУРНАЛА MAXIM.
maximonline.ru
2
LAMIAREPORT.GR
lamiareport.gr
2
MY.COM — COMMUNICATION AND ENTERTAINMENT SERVICES: MYMAIL, MAPS.ME, AND GAMES.
my.com
2
HABER ZAMANI | HABERLER ZAMANINDA OKUNUR
haberzamani.com
2
魅族官网 - 魅族 16XS 手机,极边全面屏 三摄长续航
meizu.com

Latest Sites

14
FINYA LIMITED
finyalimited.com
14
CADOCINVESTMENT.COM | AUSTRALIAN INVESTMENT COMPANY
cadocinvestment.com
14
NGF LEGAL – CORPORATE LAWYER AGENCY
ngflegal.com
14
GLOBAL LOGISTICS AUSTRALIA | GLOBAL LOGISTICS LIMITED
globallogisticslimited.com
50
THE GUY R COOK REPORT BLOG
guyrcook.com
26
CLOKIDS
clokids.shop

Top Technologies

Nginx
Web Servers
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

2 lenovo.com.cn Last Updated: 11 months

Success 39% of passed verification steps
Warning 15% of total warning
Errors 46% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 73%
Best Practices Desktop Score 69%
SEO Desktop Score 80%
Progressive Web App Desktop Score 19%
Performance Mobile Score 56%
Best Practices Mobile Score 62%
SEO Mobile Score 92%
Progressive Web App Mobile Score 56%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
Title Tag 9 Characters
官网首页
Meta Description 68 Characters
联想官方网上商城,为您提供联想笔记本电脑,平板电脑,手机,台式机,服务器,外设数码等产品在线购买及售后服务,为您提供愉悦的网上购物体验。
Effective URL 25 Characters
https://www.lenovo.com.cn
Excerpt Page content
官网首页 ...
Keywords Cloud Density
thinkpad19 lenovo7 yoga7 motorola7 english6 miix5 分体台式机4 united4 china4 ideapad4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
thinkpad 19
lenovo 7
yoga 7
motorola 7
english 6
miix 5
分体台式机 4
united 4
china 4
ideapad 4
Google Preview Your look like this in google search result
官网首页
https://www.lenovo.com.cn
联想官方网上商城,为您提供联想笔记本电脑,平板电脑,手机,台式机,服务器,外设数码等产品在线购买及售后服务,为您提供愉悦的网上购物体验。
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~257.84 KB
Code Size: ~195.05 KB
Text Size: ~62.79 KB Ratio: 24.35%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Desktop

Desktop Screenshot
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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 17.5 s
A fast page load over a cellular network ensures a good mobile user experience
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
Serve images in next-gen formats Potential savings of 3,789 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Server response times are low (TTFB) Root document took 470 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 2,266 KB
Optimized images load faster and consume less cellular data
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
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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
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
Defer offscreen images Potential savings of 4,531 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 2,177 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.0 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).
Avoid enormous network payloads Total size was 5,539 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 13 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
Avoid an excessive DOM size 1,794 elements
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)
Minify JavaScript Potential savings of 7 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 111 requests • 5,539 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 101 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 70 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 3.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive

Mobile

Mobile Screenshot
First Meaningful Paint 3.4 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 103 requests • 4,093 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 93 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 160 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 6.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
First Contentful Paint (3G) 7142 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Estimated Input Latency 20 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
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Document uses legible font sizes 94.19% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Serve images in next-gen formats Potential savings of 2,059 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid multiple page redirects Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded
Reduce server response times (TTFB) Root document took 2,020 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,830 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 926 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 30 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
Total Blocking Time 250 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.7 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
Defer offscreen images Potential savings of 746 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 1,281 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 6.5 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 4.9 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).
Avoid enormous network payloads Total size was 4,093 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 2.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 3.4 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 11 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
Avoids an excessive DOM size 586 elements
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)
Minify JavaScript Potential savings of 8 KB
Minifying JavaScript files can reduce payload sizes and script parse time

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Wed, 25 Dec 2019 06:01:45 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Server: Tengine
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: X-Requested-With
Access-Control-Allow-Methods: GET,POST,OPTIONS
Content-Encoding: gzip
Age: 18724
X-Via: 1.1 PSmgshxSJC1tb92:9 (Cdn Cache Server V2.0)
X-Ws-Request-Id: 5e02fb49_PSmgshxSJC1ol91_233960-61327
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome