Your Website Score is

Similar Ranking

46
1STDIBS: ANTIQUE AND MODERN FURNITURE, JEWELRY, FASHION & ART
1stdibs.com
46
UKRAINE INTERACTIVE MAP - UKRAINE LATEST NEWS ON LIVE MAP - LIVEUAMAP.COM
liveuamap.com
46
INSURANCE - COMPARE INSURANCE POLICY QUOTES - LIFE, CAR, HEALTH, TRAVEL
policybazaar.com
46
SINARYUDA.WEB.ID MY BLOG SPACE
sinaryuda.web.id
46
مانیتورینگ کلمات کلیدی - رتبه کلمه
rotbekalame.ir
46
ANIMATED GIF EDITOR AND GIF MAKER
ezgif.com
46
موقع الطبي للمعلومات الصحية والاستشارات الطبية | أمراض، أدوية وعلاج
altibbi.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

46 commonhealth.com.tw Last Updated: 7 months

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

Desktop

Mobile

Performance Desktop Score 65%
Best Practices Desktop Score 62%
SEO Desktop Score 91%
Progressive Web App Desktop Score 23%
Performance Mobile Score 27%
Best Practices Mobile Score 62%
SEO Mobile Score 89%
Progressive Web App Mobile Score 33%
Page Authority Authority 45%
Domain Authority Domain Authority 54%
Moz Rank 4.5/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 21 Characters
康健 - 華人世界最值得信賴的健康生活平台
Meta Description 126 Characters
《康健》,從雜誌、出版等知識傳播出發,擴大朝向全方位健康生活平台發展,提供更多元、值得信賴的內容、產品、活動與服務。匯聚最多華人地區對健康具有高度意識與興趣的優質用戶,一起實踐,也創新探索未來健康生活新型態,希望每個人都能活得自在、活得愉快、活得健康。
Effective URL 31 Characters
https://www.commonhealth.com.tw
Excerpt Page content
康健 - 華人世界最值得信賴的健康生活平台 ...
Keywords Cloud Density
立即閱讀18 康健知識庫5 控糖生活學5 特別企劃4 大人社團4 兩性關係4 康健雜誌4 瘦身減重4 關鍵90天3 返回醫療3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
立即閱讀 18
康健知識庫 5
控糖生活學 5
特別企劃 4
大人社團 4
兩性關係 4
康健雜誌 4
瘦身減重 4
關鍵90天 3
返回醫療 3
Google Preview Your look like this in google search result
康健 - 華人世界最值得信賴的健康生活平台
https://www.commonhealth.com.tw
《康健》,從雜誌、出版等知識傳播出發,擴大朝向全方位健康生活平台發展,提供更多元、值得信賴的內容、產品、活動與服務。匯聚最多華人地區對健康具有高度意識與興趣的優質用戶,一起實踐,也創新探索未來健康生活新型態,希望每個人都能活得自在、活得愉快、活得健康。
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 19 days
Page Size Code & Text Ratio
Document Size: ~222.74 KB
Code Size: ~80.22 KB
Text Size: ~142.52 KB Ratio: 63.99%

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
Reduce server response times (TTFB) Root document took 1,920 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 100 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 537 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 604 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Minimize third-party usage Third-party code blocked the main thread for 10 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.6 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 15 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
Properly size images Potential savings of 2,941 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.9 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 3.2 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 7,191 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 2.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.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 9 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,906 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
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 173 requests • 7,191 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 109 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 90 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.9 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 21.4 s
A fast page load over a cellular network ensures a good mobile user experience
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
Remove unused CSS Potential savings of 22 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 2,549 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

Mobile Screenshot
Tap targets are not sized appropriately 69% 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 98.83% 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 221 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 2,142 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 1,520 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,150 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 439 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 259 KB
Optimized images load faster and consume less cellular data
Reduce the impact of third-party code Third-party code blocked the main thread for 480 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 1,060 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 4.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
Properly size images Potential savings of 1,858 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 10.8 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 7.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 5,867 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 9.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 3.1 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 10 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,403 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
First Meaningful Paint 3.1 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 151 requests • 5,867 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 89 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 520 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 17.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 at 17.5 s
A fast page load over a cellular network ensures a good mobile user experience
First Contentful Paint (3G) 6065 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 100 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
Minify CSS Potential savings of 22 KB
Minifying CSS files can reduce network payload sizes

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
Server: nginx
Content-Type: text/html; charset=UTF-8
Vary: Accept-Encoding
Cache-Control: no-cache, private
Date: Sun, 26 Apr 2020 06:45:04 GMT
Set-Cookie: XSRF-TOKEN=eyJpdiI6InZqdjBjS25oZkNmbmNrNXAxbmdVOXc9PSIsInZhbHVlIjoidG1zTWZmN240VzBpd2VOenJqOHV5TFAzZU9nN2s4UzN4SmxzcW1NNWZKZ3N5aDUzeGRCd0VuUExma0RqaXd1USIsIm1hYyI6ImNlYWRhNDM3M2U3YWEyMjNjYjUwYjJlNGMyNDdhZDZmMzhiMTZlZGQwMjFlMGQ5NWNiNTdlNGZiMDg2ZmE4YmQifQ%3D%3D; expires=Sat, 25-Jul-2020 06:45:04 GMT; Max-Age=7776000; path=/; domain=commonhealth.com.tw; secure
Set-Cookie: commonhealth_com_tw=eyJpdiI6ImtRQXR5S3FVZ3ZUMTF5Tld2OVlxTHc9PSIsInZhbHVlIjoiYlRPenczVDIwVloxdmZaYVQ4YlFBUU5YcTk3WXZwdHgzM1M0MnkrUVFJejIyekQxVGp1RmZaNWhVakwwM2w3QyIsIm1hYyI6ImI5YzFiMzc0M2ZkMDliMWZhOGJmNTNkNTEzZTM3MTdlOTM4MDkxNGUyZDRiNTljZWU4MzAyZWNiZTMzNTdiNjUifQ%3D%3D; expires=Sat, 25-Jul-2020 06:45:04 GMT; Max-Age=7776000; path=/; domain=commonhealth.com.tw; secure; httponly
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Encoding: gzip
Via: 1.1 google
Transfer-Encoding: chunked
Alt-Svc: clear
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome