Website review, no card needed

ezhotel.com.tw logo

ezhotel.com.tw website review

Visit site (opens in a new tab)Reviewed 26 October 202634 issues · 59 checks

This review found 34 issues worth fixing on ezhotel.com.tw, 15 of them high impact, across 59 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
7.1 s1.8 sMay 9Oct 244.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.1 s
May 16, 20265.5 s
May 23, 20264.5 s
May 30, 20265.6 s
Jun 6, 20266.2 s
Jun 13, 20266.5 s
Jun 20, 20266.3 s
Jun 27, 20264.8 s
Jul 4, 20263.4 s
Jul 11, 20263.0 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.8 s
Aug 15, 20263.1 s
Aug 22, 20263.8 s
Aug 29, 20263.1 s
Sep 5, 20263.2 s
Sep 12, 20262.9 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.5 s
Oct 10, 20263.0 s
Oct 17, 20264.0 s
Oct 24, 20264.0 s

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of ezhotel.com.tw (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ezhotel.com.tw at 0.7 s0.7 s
  2. ezhotel.com.tw at 1.5 s1.5 s
  3. ezhotel.com.tw at 2.2 s2.2 s
  4. ezhotel.com.tw at 2.9 s2.9 s
  5. ezhotel.com.tw at 3.7 s3.7 s
  6. ezhotel.com.tw at 4.4 s4.4 s
  7. ezhotel.com.tw at 5.1 s5.1 s
  8. ezhotel.com.tw at 5.9 s5.9 s

Speed

9 to fix45
  • Use efficient cache lifetimes

    8.2 s · 6.5 MB

    88 files are served with short cache lifetimes, so returning visitors download them again (6.5 MB).

  • Reduce unused CSS

    5.0 s · 1.2 MB

    About 1.2 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.0 s faster on a phone.

  • Render-blocking requests

    5.9 s

    15 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.9 s.

  • Reduce unused JavaScript

    2.9 s · 611 KiB

    About 611 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

  • Font display

    2.9 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.9 s).

  • Mobile performance score: 45

    45/100

    Your mobile performance score is 45 (desktop: 39). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    750 ms · 3.5 MB

    37 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Google Analytics and others), adding 1.3 MB and 933 ms of main-thread time.

  • Google Tag Manager adds 833 ms

    833 ms

    Google Tag Manager costs a phone 833 ms of main-thread work and 1.1 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 187 ms. During a long task the page ignores taps.

  • Minify CSS

    150 ms · 30 KiB

    30 KiB could be saved by minifying CSS.

  • Minify JavaScript

    90 KiB

    90 KiB could be saved by minifying JavaScript.

  • Document request latency

    88 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 754 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix50
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • First Contentful Paint: 11.0 s

    11.0 s

    The first text or image appears after 11.0 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 29.7 s

    29.7 s

    Your largest element takes 29.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “提醒您 不碰ATM、不說個人資料 不要回覆陌生電話”.

  • Time to Interactive: 30.7 s

    30.7 s

    The page becomes fully interactive after 30.7 s. Good is under 3.8 s.

  • Speed Index: 11.7 s

    11.7 s

    Visually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.

  • Real-user LCP: 4.0 s

    4.0 s

    Real visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 2.9 s

    2.9 s

    Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.6 s

    1.6 s

    Real visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 435 ms

    435 ms

    Scripts block taps and scrolling for 435 ms in total while the page loads. Good is under 200 ms.

  • 11 images without width and height

    11 images have no width and height attributes, so the layout jumps as each one loads.

3 checks passed
  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 26% faster for real visitors

    -26%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.1 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.005

    0.005

    The layout barely moves while loading (CLS 0.005, good is under 0.1).

Images and page weight

1 to fix0
  • Page weight: 7.9 MB in 118 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 118 requests on a phone: images 4.9 MB (54), scripts 1.5 MB (28) and stylesheets 1.2 MB (15). Under 2 MB keeps phones on slow connections fast.

  • About 2.2 g of CO₂ per visit

    2.23 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.23 g of CO₂e: 267.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

2 to fix93
  • 134 text elements with low contrast

    134 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 82 links without text

    82 links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • Every image has alt text

    All 50 images in the HTML carry an alt attribute.

SEO

6 to fixGoogle 10068
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (20 characters)

    Your title is only 20 characters: “ezhotel 官網聯播網.飯店官網直訂”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://ezhotel.com.tw/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 95 internal links, 110 external

    The homepage links to 95 pages on ezhotel.com.tw and 110 external pages.

2 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “ezhotel集結官方網站直售訂房連結,訂房最安心!本服務刷卡金流由各飯店自行收取或委託品辰旅行社代收代付,消費者訂購完成請保留訂購單明細備查,有合作國旅卡之飯店於刷卡頁面將顯示國旅卡選項,請消費者預定時勾選國旅卡即可申報國旅卡訂房服務。”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://ezhotel.com.tw/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

1 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

  • Your server turned our page checks away

    1 page we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

1 to fixGoogle 9293
  • 35 distorted images

    35 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 134 words

    The homepage has only about 134 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

2 checks passed
  • 2 short forms

    2 short forms (5 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at ezhotel.com.tw, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Google Cloud

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on ezhotel.com.tw, including 19 speed issues, 6 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25