Your Website Score is

Similar Ranking

15
DECATHLON | TÜRKIYE'NIN EN BÜYÜK SPOR GIYIM VE MALZEME MAĞAZASI
decathlon.com.tr
15
北京房地产_北京房产网_北京房产信息网-北京搜狐焦点网
focus.cn
15
ГЛАВНАЯ - СИСТЕМНО-МЕТОДИЧЕСКИЙ КОМПЛЕКС
smk.edu.kz
15
SKYROCK.COM
skyrock.com
15
JIBBLE
app.jibble.io
15
TRONTV - WATCH--- VIRAL VIDEOS
trontv.com
15
CHEAP FLIGHTS, AIRLINE TICKETS AND HOTELS - JUSTFLY
justfly.com

Latest Sites

19
SEU LEITOR ONLINE DE MANHWAS, MANHUAS E WEBCOMICS YURI | YURIVERSO
yuri.live
27
AMY-SCANS | FILMES, SÉRIES, DORAMAS, ---S, OVA'S, LIVROS, MANGÁS E COMICS COM CONTEÚDO LÉSBICO
amyscans.com
19
HOME PAGE - PAUL OZYZNIEWSKI PORTFOLIO
paulthedeveloper.com
19
HOMEPAGE - THINKING THROUGH
dev.thinkingthrough.com
18

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

15 costco.com.tw Last Updated: 6 months

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

Desktop

Mobile

Performance Desktop Score 70%
Best Practices Desktop Score 62%
SEO Desktop Score 91%
Progressive Web App Desktop Score 31%
Performance Mobile Score 35%
Best Practices Mobile Score 62%
SEO Mobile Score 91%
Progressive Web App Mobile Score 33%
Page Authority Authority 41%
Domain Authority Domain Authority 49%
Moz Rank 4.1/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 33 Characters
COSTCO TAIWAN | COSTCO 好市多線上購物
Meta Description 152 Characters
好市多線上購物為Costco好市多服務各地會員所成立的網路購物平台,無論是大型傢俱、生活家電、珠寶鑽石、休閒零嘴、冷凍食品、居家用品、飲料茶水、休閒票卷,多種獨特限量海外進口商品皆在好市多線上購物。好市多線上購物提供不只是好市多賣場的衍生服務,更多的是網路獨家精選商品以及優惠活動,輕鬆擁有生活上的美好。
Effective URL 25 Characters
https://www.costco.com.tw
Excerpt Page content
Costco Taiwan | Costco 好市多線上購物 跳至內容 跳至導覽選單 ...
Keywords Cloud Density
signature11 kirkland11 辦公用品9 寵物用品8 商業配送7 居家擺飾6 辦公家具6 廚房家電6 清潔用品6 apple5
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
signature 11
kirkland 11
辦公用品 9
寵物用品 8
商業配送 7
居家擺飾 6
辦公家具 6
廚房家電 6
清潔用品 6
apple 5
Google Preview Your look like this in google search result
COSTCO TAIWAN | COSTCO 好市多線上購物
https://www.costco.com.tw
好市多線上購物為Costco好市多服務各地會員所成立的網路購物平台,無論是大型傢俱、生活家電、珠寶鑽石、休閒零嘴、冷凍食品、居家用品、飲料茶水、休閒票卷,多種獨特限量海外進口商品皆在好市多線上購物。好市多線上購物提供不只是好市多賣場的衍生服務,更多的是網路獨家精選商品以及優惠活動,輕鬆擁有生活上的美
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 / 50 years
Create on: 1970-01-01 / 50 years
Expires on: 1970-01-01 / 614 months 25 days
Page Size Code & Text Ratio
Document Size: ~271.33 KB
Code Size: ~220.53 KB
Text Size: ~50.8 KB Ratio: 18.72%

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 the impact of third-party code Third-party code blocked the main thread for 420 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 580 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.5 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 301 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 231 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.3 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 2.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 2,285 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 4.1 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.9 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 7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 12 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 4,929 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)
Preload key requests Potential savings of 320 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 113 requests • 2,285 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 79 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 600 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.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 on simulated mobile network at 16.1 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 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
Remove unused CSS Potential savings of 95 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
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Serve images in next-gen formats Potential savings of 581 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 34 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Reduce server response times (TTFB) Root document took 760 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 720 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 272 KB
Optimized images load faster and consume less cellular data

Mobile

Mobile Screenshot
Total Blocking Time 5,200 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
Defer offscreen images Potential savings of 319 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.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 11.9 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,072 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 15.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 2.5 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 7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 12 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 4,951 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)
Preload key requests Potential savings of 1,410 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
First Meaningful Paint 2.5 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 99 requests • 2,072 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 67 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 1,800 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 15.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
Page load is not fast enough on mobile networks Interactive at 15.4 s
A fast page load over a cellular network ensures a good mobile user experience
First Contentful Paint (3G) 4935 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,050 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 98% 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.06% 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 95 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
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Serve images in next-gen formats Potential savings of 518 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 34 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 120 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,290 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 255 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 3,050 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

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: Apache
X-Frame-Options: SAMEORIGIN
X-Frame-Options: SAMEORIGIN
x-xss-protection: 1; mode=block
Pragma: no-cache
X-Content-Type-Options: nosniff
Content-Language: zh-TW
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Type: text/html;charset=UTF-8
Content-Length: 39895
Cache-Control: no-cache, no-store, must-revalidate
Expires: Mon, 13 Jan 2020 16:45:11 GMT
Date: Mon, 13 Jan 2020 16:45:11 GMT
Connection: keep-alive
Strict-Transport-Security: max-age=31536000 ; includeSubDomains ; preload
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome