pacificcross.com.ph website review

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

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

8 third-party services load with your homepage (Google Tag Manager, website-files.com and Facebook and others), adding 3.3 MB and 906 ms of main-thread time.

5 files are served with short cache lifetimes, so returning visitors download them again (166 KiB).

Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.

3 images could be 881 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

website-files.com costs a phone 123 ms of main-thread work and 2.3 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.

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

Polyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

About 22 KiB of CSS is downloaded but never applied on this page.

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 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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

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

Your homepage downloads 3.3 MB in 42 requests on a phone: images 2.0 MB (18), scripts 1.1 MB (14) and fonts 162 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

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

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

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

The homepage links to 87 pages on pacificcross.com.ph and 22 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.pacificcross.com.ph/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.

https://www.pacificcross.com.ph/insurance-plan/blue-royale, https://www.pacificcross.com.ph/insurance-plan/select, https://www.pacificcross.com.ph/insurance-plan/vanguard, https://www.pacificcross.com.ph/insurance-plan/flexi-shield, https://www.pacificcross.com.ph/insurance-plan/bc-flexi-access and https://www.pacificcross.com.ph/insurance-plan/bc-flexi-baby-group and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.

3 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 1,134 words of visible text.

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 3 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.