Gome.com.cn - SEO Checker - Website Review

Your Website Score is

Similar Ranking

MARKETING EYE BRISBANE | NEXT LEVEL MARKETING AGENCY

marketingeyebrisbane.com.au

LAYER CHICKEN CAGE

poultrymachine.com

FILERIO : : CLOUD FILE STORAGE - EASY WAY TO SHARE YOUR FILES

filerio.in

GROW YOUR BUSINESS WITH CONTESTS & SOCIAL MARKETING APPS

gleam.io

TERCEIRO Z - HENTAI, INCESTO, PORNÔ, QUADRINHOS ERÓTICOS E MUITO MAIS!

terceiroz.com

ERROR: THE REQUESTED URL COULD NOT BE RETRIEVED

qhnky.com

METASRC PATCH 9.24 HOME - 5V5

metasrc.com

Latest Sites

i72tq6h2fsoku1o5.onion

MONTHJOB - GET PAID FOR SUBSCRIPTIONS WITH FREE NEWSLETTERS

monthjob.com

eurobux.biz

OFFICIAL SITE - ZAAPTV - MAAXTV - ARAABTV - AUSTRALIA & N.Z

globetv.com.au

GIFTS AUSTRALIA WILL HELP TO FIND THE BEST GIFT QUICKLY FOR EVERY OCCASION!

giftsaustralia.com.au

FAN+ OFFERS FANS ACCESS TO EXTRAORDINARY EXPERIENCES

fanplus.com

FURNITURE SHOP ONLINE IN AUSTRALIA | CHEAP & AFFORDABLE - DREAMO LIVING

dreamo.com.au

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

19 gome.com.cn Last Updated: 2 years

Success 70% of passed verification steps

Warning 7% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 73%

Best Practices Desktop Score 77%

SEO Desktop Score 82%

Progressive Web App Desktop Score 46%

Performance Mobile Score 39%

Best Practices Mobile Score 62%

SEO Mobile Score 89%

Progressive Web App Mobile Score 26%

Page Authority Authority 0%

Domain Authority Domain Authority 0%

Moz Rank 0.0/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 36 Characters

国美(GOME)-综合网购商城，正品低价、品质保障、快速送达、安心服务！

Meta Description 108 Characters

国美(Gome.com.cn)国美电器唯一官方网上商城，中国领先的专业家电网购平台.全球品牌电视、洗衣机、电脑、手机、数码、空调、电脑配件、生活电器、网络产品等正品行货，更低价格，更快送达，为您提供便捷、诚信的服务.

Effective URL 23 Characters

https://www.gome.com.cn

Excerpt Page content

国美(GOME)-综合网购商城，正品低价、品质保障、快速送达、安心服务！ ...

Meta Keywords 13 Detected

国美国美在线国美电器国美官方旗舰店国美电器网上商城电视洗衣机电脑手机数码空调电脑配件生活电器

Keywords Cloud Density

上门服务4 家居家装3 我的收藏2 快速响应2 国美管家2 国美会员2 随时预约2 安全更便捷2 购物保障1 购物流程1

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
上门服务	4
家居家装	3
我的收藏	2
快速响应	2
国美管家	2
国美会员	2
随时预约	2
安全更便捷	2
购物保障	1
购物流程	1

Google Preview Your look like this in google search result

国美(GOME)-综合网购商城，正品低价、品质保障、快速送达、安心服务！

https://www.gome.com.cn

Robots.txt File Detected

http://gome.com.cn/robots.txt

Sitemap.xml File Detected

http://gome.com.cn/sitemap.xml

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 / 52 years

Create on: 1970-01-01 / 52 years

Expires on: 1970-01-01 / 627 months 23 days

Nameservers

ns3.dnsv5.com

ns4.dnsv5.com

Page Size Code & Text Ratio

Document Size: ~124.86 KB

Code Size: ~124.31 KB

Text Size: ~560 B Ratio: 0.44%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Desktop

Reduce server response times (TTFB) Root document took 1,670 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 270 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 3 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Efficiently encode images Potential savings of 270 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

Defer offscreen images Potential savings of 29 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

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 7.0 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 0.7 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 927 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimizes main-thread work 1.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 0.6 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 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

Avoid an excessive DOM size 914 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 0.6 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 48 requests • 927 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 38 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 60 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 0.7 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

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 13 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 387 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

Mobile

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,410 ms

Redirects introduce additional delays before the page can be loaded

Reduce server response times (TTFB) Root document took 1,020 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 1,170 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 573 KB

Optimized images load faster and consume less cellular data

Enable text compression Potential savings of 2 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Total Blocking Time 290 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 1.6 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 1,689 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 562 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 9.9 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 5.3 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 2,536 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 7.3 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.2 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 14 chains found

Avoids an excessive DOM size 700 elements

First Meaningful Paint 3.2 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 112 requests • 2,536 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Use video formats for animated content Potential savings of 69 KB

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes

Serve static assets with an efficient cache policy 85 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 220 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 10.3 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 10.3 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 30 ms

First Contentful Paint (3G) 6227 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Tap targets are not sized appropriately 76% 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 78.21% 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 29 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,209 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

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

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
Server: GOMEWS
Date: Mon, 23 Dec 2019 18:30:09 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
X-Info: s1sw010 s1sw015
Vary: Accept-Encoding
Access-Control-Allow-Origin: *
Access-Control-Allow-Credentials: true
Access-Control-Allow-Methods: GET, POST, OPTIONS, PUT, DELETE
Access-Control-Allow-Headers: DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type
Set-Cookie: uid=CjozKF4BB7Et7JX6O3WmAg==; expires=Sat, 28-Dec-19 18:30:09 GMT; domain=gome.com.cn; path=/
P3P: policyref="/w3c/p3p.xml", CP="CUR ADM OUR NOR STA NID"
Content-Encoding: gzip

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	gome.com.cn	124.250.72.168	IN	463
NS	gome.com.cn	ns3.dnsv5.com	IN	85520
NS	gome.com.cn	ns4.dnsv5.com	IN	85520
MX	gome.com.cn	mail.gome.com.cn	IN	600
MX	gome.com.cn	mx3.gome.com.cn	IN	60
TXT	gome.com.cn	webexdomainverification.7857737d84962b17e0536b15fe0a47c0=a409ada4-fe70-4526-9241-c6c1232d2b44	IN	600
TXT	gome.com.cn	webexdomainverification.7857737d84942b17e0536b15fe0a47c0=58d94135-9803-4cf5-acdc-46959558194e	IN	600
TXT	gome.com.cn	webexdomainverification.7857737d84982b17e0536b15fe0a47c0=6ee15870-3271-412b-aa6a-d5316447f9f5	IN	600
TXT	gome.com.cn	v=spf1 ip4:115.182.95.72 ip4:115.182.95.98 ip4:115.182.95.120 ~all	IN	600
TXT	gome.com.cn	webexdomainverification.4F40C8799ED45713E0536B15FE0A7FEF=b5eb2552-be5f-46ea-bc16-c0b7ac91cb1f	IN	600

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

19 gome.com.cn Last Updated: 2 years

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments