Your Website Score is

Similar Ranking

50
VIDIO.COM - VIDEO DAN TV--- DI INDONESIA
vidio.com
50
BÁO ĐIỆN TỬ VTV NEWS - ĐÀI TRUYỀN HÌNH VIỆT NAM | VTV.VN
vtv.vn
50
CELTRA CREATIVE MANAGEMENT PLATFORM | MASTER YOUR DIGITAL AD CREATIVE
celtra.com
50
HOME | THE TOKYO ORGANISING COMMITTEE OF THE OLYMPIC AND PARALYMPIC GAMES
tokyo2020.org
50
IMÓVEIS, CASAS E APARTAMENTOS PARA COMPRA, VENDA E ALUGUEL - VIVA REAL
vivareal.com.br
50
CODEMENTOR | GET LIVE 1:1 CODING HELP, HIRE A DEVELOPER, & MORE
codementor.io
50
ENGLISH EXERCISES: GRAMMAR, LISTENING, READING...
agendaweb.org

Latest Sites

19
PINOY MOVIES - WATCH PINOY MOVIES ONLINE---
cineko.to
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

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

50 apple.com.cn Last Updated: 12 months

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

Desktop

Mobile

Performance Desktop Score 66%
Best Practices Desktop Score 69%
SEO Desktop Score 100%
Progressive Web App Desktop Score 19%
Performance Mobile Score 28%
Best Practices Mobile Score 77%
SEO Mobile Score 98%
Progressive Web App Mobile Score 22%
Page Authority Authority 50%
Domain Authority Domain Authority 76%
Moz Rank 5.0/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 19 Characters
APPLE (中国大陆) - 官方网站
Meta Description 79 Characters
探索 Apple 充满创新的世界,选购各式 iPhone、iPad、Apple Watch 和 Mac,浏览各种配件、娱乐产品,并获得相关产品的专家支持服务。
Effective URL 19 Characters
http://apple.com.cn
Excerpt Page content
Apple (中国大陆) - 官方网站 Apple (中国大陆) - 官方网站 Global Nav 打开菜单 Global Nav 关闭菜单 Ap...
Keywords Cloud Density
apple29 打开菜单9 关闭菜单9 进一步了解7 iphone5 store5 watch4 64gb4 ipad3 music3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
apple 29
打开菜单 9
关闭菜单 9
进一步了解 7
iphone 5
store 5
watch 4
64gb 4
ipad 3
music 3
Google Preview Your look like this in google search result
APPLE (中国大陆) - 官方网站
http://apple.com.cn
探索 Apple 充满创新的世界,选购各式 iPhone、iPad、Apple Watch 和 Mac,浏览各种配件、娱乐产品,并获得相关产品的专家支持服务。
Robots.txt File Detected
Sitemap.xml File Detected
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
Updated: 1970-01-01 / 51 years
Create on: 1970-01-01 / 51 years
Expires on: 1970-01-01 / 619 months 22 days

Nameservers
nserver.apple.com
nserver.asia.apple.com
nserver2.apple.com
Page Size Code & Text Ratio
Document Size: ~83.68 KB
Code Size: ~66.09 KB
Text Size: ~17.58 KB Ratio: 21.01%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Server response times are low (TTFB) Root document took 70 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 750 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 129 KB
Optimized images load faster and consume less cellular data
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.3 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
Speed Index 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 3.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).
Avoid enormous network payloads Total size was 3,703 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.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 1.2 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 28 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 724 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)
First Meaningful Paint 3.5 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 97 requests • 3,703 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 64 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 30 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.5 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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 16.4 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
Remove unused CSS Potential savings of 10 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 458 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 530 ms
Redirects introduce additional delays before the page can be loaded
Does not use HTTPS 2 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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

Mobile

Mobile Screenshot
Serve static assets with an efficient cache policy 84 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 190 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 14.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
Page load is not fast enough on mobile networks Interactive at 14.8 s
A fast page load over a cellular network ensures a good mobile user experience
First Contentful Paint (3G) 8445 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 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
Tap targets are not sized appropriately 89% 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 99.74% 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
Remove unused CSS Potential savings of 41 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 1,111 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
Does not use HTTPS 2 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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
Avoid multiple page redirects Potential savings of 1,740 ms
Redirects introduce additional delays before the page can be loaded
Server response times are low (TTFB) Root document took 80 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,980 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 111 KB
Optimized images load faster and consume less cellular data
Total Blocking Time 660 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 2.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 17 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 5.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 14.8 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,461 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 8.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 4.2 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 28 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 724 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)
First Meaningful Paint 14.8 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 117 requests • 4,461 KB
To set budgets for the quantity and size of page resources, add a budget.json file

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


						
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome