payeasy.com.tw website review

The page goes through 1 redirect before it starts loading, costing about 2.9 s. Link and advertise the final URL directly.

About 303 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.

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

About 534 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 480 ms faster on a phone.

34 KiB could be saved by minifying CSS.

A phone's processor spends 2.8 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

1 third-party service load with your homepage (Unpkg), adding 64 KiB and 0 ms of main-thread time.

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.

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

Your largest element takes 37.5 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 137 ms to 148 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 22.7 MB in 236 requests on a phone: images 19.4 MB (124), scripts 1.6 MB (56) and fonts 1.3 MB (20). Under 2 MB keeps phones on slow connections fast.

8 images weigh 13.4 MB together. On a phone connection a single image that size takes seconds.

20 images are downloaded at several times the size a phone draws them, for example img_hero_purchase.png at 1,575 px wide, shown at 390 px. Resized copies would save about 5.1 MB.

40 images (18.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

35 images further down the page (7.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

18 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.

Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is only 24 characters: “PayEasy�U����̤j���~�֧Q��”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 7 pages on payeasy.com.tw and 7 external pages.

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.

There is no https://www.payeasy.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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.payeasy.com.tw/pbenefit/in_other/pmedm/app, whose canonical is https://www.payeasy.com.tw/pbenefit/in_other/pmedm/app/index.htm. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.payeasy.com.tw/pbenefit/in_other/pmedm/app, https://www.payeasy.com.tw/cs and https://www.payeasy.com.tw/pbenefit/in_other/pmedm/identity/new/index.html have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.payeasy.com.tw/pbenefit/in_other/pmedm/app and https://www.payeasy.com.tw/pbenefit/in_other/pmedm/identity/new/index.html have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 3 pages linked from your homepage and read each the way a search engine does.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 14 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.