gap.com.ph website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, TikTok and tabarn.app and others), adding 10.3 MB and 1.2 s of main-thread time.

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

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

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

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

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

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

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

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

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

11 KiB could be saved by minifying CSS.

9 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

Your homepage downloads 25.3 MB in 330 requests on a phone: media 20.4 MB (2), images 2.1 MB (50) and scripts 1.6 MB (94). Under 2 MB keeps phones on slow connections fast.

I8_HAMNAV_TXT.svg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images are downloaded at several times the size a phone draws them, for example DIVISION_BANNER_2026_Kids_2bbb0b89-2cc7-4726-a89b-6f5826304e at 610 px wide, shown at 174 px. Resized copies would save about 86 KiB.

7 images (461 KiB) 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.

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

133 elements have a tabindex above 0, which scrambles the keyboard order.

5 buttons have no accessible name, so screen readers announce just “button”.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Some lists contain elements other than list items, which screen readers announce wrongly.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

10 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is 76 characters, so Google will cut it off around 60: “Shop Gap for Casual Women's, Men's, Toddler & Kids Clothes - Gap Philippines”.

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

There are 9 <h1> headlines (“New”, “Women” and “Men”). One clear main headline is easier for people and search engines.

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

The homepage links to 415 pages on gap.com.ph and 10 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.

/pages/vip-page, /pages/my-gap-page, /collections/women-new-arrivals, /collections/men-new-arrivals, /collections/gap-girls-new-arrivals-1 and /collections/boys-new-arrivals and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/men-new-arrivals took over 3 s to send its HTML from our server.

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

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Unexpected token ';'”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Requests the notification permission on page load.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

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.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

gap.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.

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

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 734 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

DMARC is set to p=none, so mail pretending to be gap.com.ph is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 mores (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 21 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.