Your Website Score is

Similar Ranking

31
国联资源网_中国领先的B2B电子商务集群,高效的链商资源整合服务网络
ibicn.com
31
REVOLVE (リボルブ)で、有名デザイナーズブランドの洋服をショッピング
revolveclothing.co.jp
31
VOITURE AU MAROC - VOITURE OCCASION AU MAROC - ANNONCES MOTEUR.MA
moteur.ma
31
مكتبة نور - تحميل كتب PDF
noor-book.com
31
BEST WIFI BROADBAND & INTERNET SERVICE PROVIDER (ISP) IN INDIA | TIKONA INFINET PRIVATE LIMITED
tikona.in
31
DOWNLOAD--- SOFTWARE FOR WINDOWS - JALECO.COM
jaleco.com
31
نماشا - سرویس رایگان اشتراک ویدیو
namasha.com

Latest Sites

14
PORTSTONE PARTNERS LIMITED
portstonepartnersltd.com
14
VENICTRADE.COM
venictrade.com
14
COINLUNO.COM
coinluno.com
14
SIGNCURRENCY.COM
signcurrency.com
14
ALLTRADESFX.COM
alltradesfx.com
19
MODERN KITCHENS | READIKIT | HOME PAGE
readikit.com
1

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

31 edh.tw Last Updated: 11 months

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

Desktop

Mobile

Performance Mobile Score 20%
Best Practices Mobile Score 62%
SEO Mobile Score 82%
Progressive Web App Mobile Score 41%
Page Authority Authority 17%
Domain Authority Domain Authority 37%
Moz Rank 1.7/10
Bounce Rate Rate 0%
Title Tag 15 Characters
早安健康-每天都做得到的健康
Meta Description 85 Characters
早安健康相信,健康的方式不只是治療疾病,更多的是快樂的心境、好好生活,做得到的健康,才會在每一天產生新力量。我們相信,尊敬大自然、呼應身體的訊息,才能找到正確的療癒方式。
Effective URL 18 Characters
https://www.edh.tw
Excerpt Page content
早安健康-每天都做得到的健康 【感謝有你 健康相伴】早安健康訂一年送一年共24期加送頂級316不鏽鋼保鮮盒三件組,超值優惠價1990元立即搶購 X ...
Keywords Cloud Density
今日熱門文章9 精選文章9 more6 你常吃的可能也中標5 把握2020金鼠年5 生肖運勢5 含植物油食品恐藏致癌物5 更多>>5 做對努力有機會旺十二年4 早安健康4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
今日熱門文章 9
精選文章 9
more 6
你常吃的可能也中標 5
把握2020金鼠年 5
生肖運勢 5
含植物油食品恐藏致癌物 5
更多>> 5
做對努力有機會旺十二年 4
早安健康 4
Google Preview Your look like this in google search result
早安健康-每天都做得到的健康
https://www.edh.tw
早安健康相信,健康的方式不只是治療疾病,更多的是快樂的心境、好好生活,做得到的健康,才會在每一天產生新力量。我們相信,尊敬大自然、呼應身體的訊息,才能找到正確的療癒方式。
Robots.txt File Detected
Sitemap.xml File No Found
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 / 618 months 20 days
Page Size Code & Text Ratio
Document Size: ~342.07 KB
Code Size: ~209.18 KB
Text Size: ~132.89 KB Ratio: 38.85%

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

Mobile

Mobile Screenshot
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 147 requests • 2,946 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 16 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 1,920 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 21.6 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 21.6 s
A fast page load over a cellular network ensures a good mobile user experience
First Contentful Paint (3G) 6360 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 1,150 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 3 KB
Minifying CSS files can reduce network payload sizes
Tap targets are not sized appropriately 94% 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.8% 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 135 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 480 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
User Timing marks and measures 16 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 400 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 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 636 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 257 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 4,450 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 3,020 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 7.8 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 630 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 13.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 18.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 2,946 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 12.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 3.2 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 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
Avoid an excessive DOM size 2,106 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 38 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
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Cache-Control: no-cache="set-cookie"
Content-Encoding: gzip
Content-Language: en
Date: Tue, 26 Nov 2019 13:54:46 GMT
Server: nginx
Set-Cookie: AWSELB=3F8D11CB12A1C8BA9F935AD6CC1E890B35DCD4EB7B3AB8D568070225B547E002675AC9C8F29FEFD344E5460869CBFC1295F0ED6D4448CA647CA096A3896A6539961CABD37E;PATH=/;MAX-AGE=86400
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Frame-Options: SAMEORIGIN
X-Cache: Miss from cloudfront
Via: 1.1 98e2eb12ca62ecc662bc928ec41abedd.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: ORD52-C2
X-Amz-Cf-Id: 5VKMo0hP1abavH6OV3yZ5jCFAZ3nRnmYwxf_jNiPh7cv9wJsx6eerQ==
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome