Google.com.tw - SEO Checker

Your Website Score is

Similar Ranking

TRANSFER MONEY ONLINE | SEND MONEY ABROAD WITH TRANSFERWISE

transferwise.com

CONSERVATIVE NEWS MEDIA & PUBLISHER | BIZPAC REVIEW

bizpacreview.com

TRADEINDIA - INDIAN EXPORTERS, MANUFACTURERS, SUPPLIERS DIRECTORY, B2B BUSINESS DIRECTORY

tradeindia.com

PROPERTY IN INDIA - BUY PROPERTIES IN INDIA, REAL ESTATE WEBSITE FOR INDIA PROPERTY - CALL US - +91 92788 92788

proptiger.com

CLUBE DO HARDWARE - CLUBE DO HARDWARE

clubedohardware.com.br

INDEX.HR

index.hr

PAYPAY - QRコード・バーコードで支払うスマホ決済アプリ

paypay.ne.jp

Latest Sites

HOME - DREXESCROW

drexescrow.com

AMERICA NO.1 RAMEN MALL

ramenmall.com

SEARCH FOR WHOLESALE PRODUCTS WHOLESALE | SUPPLY LEADER — WHOLESALE SUPPLY

supplyleader.com

home.takepocket.com

ENGINEERING DESTINATION

engineeringdestination.com

BITINCOME.PRO

bitincome.pro

SIMPLY EARN MONEY | MONEY EARNING IDEAS

simplyearnmoney.com

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

56 google.com.tw Last Updated: 1 year

Success 47% of passed verification steps

Warning 30% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 100%

Best Practices Desktop Score 92%

SEO Desktop Score 82%

Progressive Web App Desktop Score 46%

Performance Mobile Score 93%

Best Practices Mobile Score 85%

SEO Mobile Score 90%

Progressive Web App Mobile Score 56%

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 6 Characters

GOOGLE

Meta Description 159 Characters

Search the world's information, including webpages, images, videos and more. Google has many special features to help you find exactly what you're looking for.

Effective URL 37 Characters

https://www.google.com.tw/?gws_rd=ssl

Excerpt Page content

Google.. About Store GmailImagesSign in Remove Report inappropriate predictions ×Who left the lights on at the North Pole? See how little elves have a big impactGoogle offered in: 中文（繁體） PrivacyTermsSettingsSearc...

Keywords Cloud Density

search5 settings2 about1 google1 business1 advertising1 feedback1 send1 help1 history1

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

Keyword	Freq	Title	Desc	Domain	H1	H2
search	5
settings	2
about	1
google	1
business	1
advertising	1
feedback	1
send	1
help	1
history	1

Google Preview Your look like this in google search result

GOOGLE

https://www.google.com.tw/?gws_rd=ssl

Search the world's information, including webpages, images, videos and more. Google has many special features to help you find exactly what you're loo

Robots.txt File Detected

http://google.com.tw/robots.txt

Sitemap.xml File Detected

http://google.com.tw/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 / 51 years

Create on: 1970-01-01 / 51 years

Expires on: 1970-01-01 / 626 months 20 days

Page Size Code & Text Ratio

Document Size: ~220.98 KB

Code Size: ~160.96 KB

Text Size: ~60.02 KB Ratio: 27.16%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

Google Web Server

Web Servers

PWA - Manifest

Manifest is not valid

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

Desktop

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

User Timing marks and measures 4 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Server response times are low (TTFB) Root document took 300 ms

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

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 30 ms

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

JavaScript execution time 0.2 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 0.6 s

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

First CPU Idle 0.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).

Avoids enormous network payloads Total size was 586 KB

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

Minimizes main-thread work 0.4 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.5 s

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

Avoid chaining critical requests 2 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 225 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.5 s

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

Keep request counts low and transfer sizes small 18 requests • 586 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 79 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

Uses efficient cache policy on static assets 0 resources found

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

Max Potential First Input Delay 100 ms

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

Mobile

Uses efficient cache policy on static assets 0 resources found

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

Max Potential First Input Delay 320 ms

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

Time to Interactive 4.4 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 80 ms

First Contentful Paint (3G) 2263 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 95% 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 100% 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

User Timing marks and measures 2 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

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

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 380 ms

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

JavaScript execution time 1.0 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 5 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 1.2 s

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

First CPU Idle 3.6 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 463 KB

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

Minimizes main-thread work 1.7 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 1 chain found

Avoids an excessive DOM size 437 elements

First Meaningful Paint 1.3 s

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

Keep request counts low and transfer sizes small 22 requests • 463 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 79 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

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
Date: Mon, 23 Dec 2019 09:33:47 GMT
Expires: -1
Cache-Control: private, max-age=0
Content-Type: text/html; charset=UTF-8
Strict-Transport-Security: max-age=31536000
P3P: CP="This is not a P3P policy! See g.co/p3phelp for more info."
Content-Encoding: gzip
Server: gws
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Set-Cookie: 1P_JAR=2019-12-23-09; expires=Wed, 22-Jan-2020 09:33:47 GMT; path=/; domain=.google.com.tw; SameSite=none
Set-Cookie: NID=194=ckdjAFr-eWH3yA3Z8mADIpKzkxlTxNsnS4fcFHQl_RJQhC6seLNW0S6VsmAzDak7Go2BkrhHfbNXB2uxy9kO4z00y7mffi9jJ-CPCxuzxAMg7nSDbo9z27twBhYLnTRTVDANWvwkWtCHUTpbK3779fJIMx65mdNAbTF3N150Pw4; expires=Tue, 23-Jun-2020 09:33:47 GMT; path=/; domain=.google.com.tw; HttpOnly
Transfer-Encoding: chunked
Alt-Svc: quic=":443"; ma=2592000; v="46,43",h3-Q050=":443"; ma=2592000,h3-Q049=":443"; ma=2592000,h3-Q048=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	google.com.tw	172.217.7.3	IN	274
NS	google.com.tw	ns3.google.com	IN	3428
NS	google.com.tw	ns1.google.com	IN	3428
NS	google.com.tw	ns4.google.com	IN	3428
NS	google.com.tw	ns2.google.com	IN	3428
MX	google.com.tw	alt2.aspmx.l.google.com	IN	600
MX	google.com.tw	alt3.aspmx.l.google.com	IN	600
MX	google.com.tw	alt4.aspmx.l.google.com	IN	600
MX	google.com.tw	aspmx.l.google.com	IN	600
MX	google.com.tw	alt1.aspmx.l.google.com	IN	600
TXT	google.com.tw	v=spf1 -all	IN	300
AAAA	google.com.tw	2607:f8b0:4006:800::2003	IN	274

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

56 google.com.tw Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Google Web Server

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments