ecpay.com.ph website review

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

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

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

46 images could be 7.8 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.

About 151 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

Your mobile performance score is 62 (desktop: 63). Pages that score under 90 lose visitors before the first paint.

43 KiB could be saved by minifying JavaScript.

Google Tag Manager costs a phone 194 ms of main-thread work and 511 KiB 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.

FontAwesome CDN costs a phone 69 ms of main-thread work and 490 KiB 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.

3 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Google Analytics), adding 1,001 KiB and 263 ms of main-thread time.

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

Polyfills for old browsers add 6 KiB JavaScript that modern phones do not need.

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

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.

Your largest element takes 41.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ecTransact Transact Now”.

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

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

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

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

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

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

The layout shifts by 0.104 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 13.6 MB in 159 requests on a phone: images 11.6 MB (83), scripts 1.2 MB (58) and fonts 640 KiB (8). Under 2 MB keeps phones on slow connections fast.

31 images are downloaded at several times the size a phone draws them, for example MANILAWATER.jpg at 3,000 px wide, shown at 330 px. Resized copies would save about 7.3 MB.

6 images weigh 5.5 MB together. On a phone connection a single image that size takes seconds.

40 images (10.4 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.

38 images further down the page (10.2 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 3.86 g of CO₂e: 463.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

4 tap targets are too small or too close together to hit reliably with a finger.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings skip levels (h2 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.

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

Your title is only 5 characters: “ECPay”. 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 276 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 48 pages on ecpay.com.ph 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 /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.

/service-update, /ecpartners/ecbills, /ecpartners/eccash, /ecpartners/ecload, /ecpartners/ecpins and /ecpartners/eccashout and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

/service-update has no <h1> headline, so visitors and search engines get no clear main topic.

/service-update has 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 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 link from your homepage to your own site is broken, for example https://ecpay.com.ph/cdn-cgi/l/email-protection (404).

2 links go through two or more redirects, for example https://ecpayphhelpdesk.freshdesk.com/support/login.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

ecpay.com.ph has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Social proof on the homepage: 11 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

The homepage carries about 542 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 2 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.