raptor.ph website review

About 3.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 16.6 s faster on a phone.

YouTube costs a phone 1.8 s of main-thread work and 4.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (YouTube, Shopify and avada.io and others), adding 7.1 MB and 2.5 s of main-thread time.

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

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

Shopify costs a phone 294 ms of main-thread work and 1.5 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.

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

64 KiB could be saved by minifying JavaScript.

The page has 2,418 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

avada.io costs a phone 89 ms of main-thread work and 333 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.

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

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

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

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

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 22.9 s on a phone. Good is under 1.8 s.

Your largest element takes 39.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

Real visitors wait 292 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

Your homepage downloads 11.3 MB in 482 requests on a phone: scripts 6.1 MB (161), images 2.8 MB (66) and other files 1,014 KiB (158). Under 2 MB keeps phones on slow connections fast.

5 images (1.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.

2 images are downloaded at several times the size a phone draws them, for example 300x_divider_5.jpg at 2,000 px wide, shown at 80 px. Resized copies would save about 170 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (6 elements).

There are 4 <h1> headlines (“New Release”, “Featured Products” and “Born from Passion, Built to Last”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("#")”.

The homepage links to 284 pages on raptor.ph and 17 external pages.

https://raptor.ph/collections/all, https://raptor.ph/policies/shipping-policy, https://raptor.ph/collections/new-release-products and https://raptor.ph/collections/promo have no meta description, so Google writes the search snippet from whatever text it finds.

https://raptor.ph/products/raptor-archipelago-shirt-mt-pulag-raptor-ph and https://raptor.ph/products/raptor-archipelago-shirt-mt-apo-raptor-ph use the same meta description. A description written for each page earns more clicks.

https://raptor.ph/collections/all, https://raptor.ph/collections/new-release-products, https://raptor.ph/pages/brand-story, https://raptor.ph/blogs/news, https://raptor.ph/pages/corporate-sales and https://raptor.ph/pages/be-a-dealer and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://raptor.ph/blogs/news, https://raptor.ph/pages/contact, https://raptor.ph/pages/corporate-sales and https://raptor.ph/pages/be-a-dealer took over 3 s to send their HTML from our server.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

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

The homepage carries about 1,148 words of visible text.

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