Programmable

Website review, no card needed

western.com.ph logo

western.com.ph website review

Visit site (opens in a new tab)Reviewed 23 October 202634 issues · 77 checks

This review found 34 issues worth fixing on western.com.ph, 12 of them high impact, across 77 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

72C

Closest competitors among WooCommerce stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
5.5 s1.9 sMay 2Oct 175.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.4 s
May 9, 20262.4 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.4 s
Jun 6, 20262.8 s
Jun 13, 20263.2 s
Jun 20, 20263.7 s
Jun 27, 20264.0 s
Jul 4, 20263.9 s
Jul 11, 20263.9 s
Jul 18, 20263.9 s
Jul 25, 20263.9 s
Aug 1, 20263.9 s
Aug 8, 20264.0 s
Aug 15, 20264.1 s
Aug 22, 20264.1 s
Aug 29, 20264.1 s
Sep 5, 20264.1 s
Sep 12, 20264.1 s
Sep 19, 20264.2 s
Sep 26, 20264.5 s
Oct 3, 20264.6 s
Oct 10, 20264.9 s
Oct 17, 20265.0 s
Real-visitor tap response (INP)75th percentile, phones
275 ms171 msMay 2Oct 17263 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026189 ms
May 9, 2026187 ms
May 16, 2026185 ms
May 23, 2026183 ms
May 30, 2026185 ms
Jun 6, 2026189 ms
Jun 13, 2026195 ms
Jun 20, 2026201 ms
Jun 27, 2026209 ms
Jul 4, 2026212 ms
Jul 11, 2026211 ms
Jul 18, 2026211 ms
Jul 25, 2026214 ms
Aug 1, 2026216 ms
Aug 8, 2026220 ms
Aug 15, 2026223 ms
Aug 22, 2026222 ms
Aug 29, 2026223 ms
Sep 5, 2026226 ms
Sep 12, 2026226 ms
Sep 19, 2026230 ms
Sep 26, 2026232 ms
Oct 3, 2026233 ms
Oct 10, 2026247 ms
Oct 17, 2026263 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

western.com.ph (opens in a new tab)
Full-page screenshot of western.com.ph (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. western.com.ph at 0.4 s0.4 s
  2. western.com.ph at 0.8 s0.8 s
  3. western.com.ph at 1.1 s1.1 s
  4. western.com.ph at 1.5 s1.5 s
  5. western.com.ph at 1.9 s1.9 s
  6. western.com.ph at 2.3 s2.3 s
  7. western.com.ph at 2.6 s2.6 s
  8. western.com.ph at 3.0 s3.0 s

Speed

7 to fix56

  • 4,254 HTML elements

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

  • Document request latency

    750 ms · 691 KiB

    The HTML itself could arrive about 750 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Mobile performance score: 56

    56/100

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

  • Reduce initial server response time

    747 ms

    Reduce initial server response time. Google estimates savings of 747 ms on a phone.

  • 1 third-party service on the page

    1 third-party service load with your homepage (nitrocdn.com), adding 1.1 MB and 0 ms of main-thread time.

  • nitrocdn.com adds 0 ms

    0 ms

    nitrocdn.com costs a phone 0 ms of main-thread work and 1.1 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.

  • Server response: 847 ms

    847 ms

    Your server takes 847 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Reduce unused CSS

    208 KiB

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

  • 3 long tasks on the main thread

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

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed

  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 170 ms of it running JavaScript. That is comfortably low.

Core Web Vitals

11 to fix33

  • Fails Core Web Vitals for real visitors

    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.

  • Real-user LCP: 6.5 s

    6.5 s

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

  • Real-user FCP: 6.2 s

    6.2 s

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

  • Real-user TTFB: 4.6 s

    4.6 s

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

  • First Contentful Paint: 10.9 s

    10.9 s

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

  • Largest Contentful Paint: 11.8 s

    11.8 s

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

  • Speed Index: 10.9 s

    10.9 s

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

  • Time to Interactive: 11.8 s

    11.8 s

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

  • Real-user INP: 303 ms

    303 ms

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

  • Tap response (INP) got 36% slower for real visitors

    +36%

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

  • Largest content (LCP) got 110% slower for real visitors

    +110%

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

3 checks passed

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0.002

    0.002

    The layout barely moves while loading (CLS 0.002, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85

  • Page weight: 3.4 MB in 97 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 97 requests on a phone: other files 1.2 MB (69), HTML 1.0 MB (1) and fonts 826 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.95 g

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

3 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9195

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Page should contain a level-one heading (1 element)

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 16 links without text

    16 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 (2 elements)

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

  • Headings skip levels

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

2 checks passed

  • Every image has alt text

    All 221 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8577

  • No H1 headline

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

  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “Western Appliances | Home & Kitchen Appliances Store Manila, Philippines”.

  • Structured data has 1 problem

    Structured data found (Corporation, SiteNavigationElement and WebSite) but with 1 problem, for example “Corporation: sameAs is an empty list”.

  • 7 links with vague text

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

  • 554 internal links, 9 external

    The homepage links to 554 pages on western.com.ph and 9 external pages.

5 checks passed

  • Meta description: 144 characters

    Your meta description is 144 characters: “Western Appliances is a reputable appliance store with branches in Metro Manila and other areas. We carry various produ…”.

  • Canonical URL set

    The canonical URL is https://western.com.ph/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://western.com.ph/sitemap_index.xml.

AI search readiness

100

  • No llms.txt

    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.

3 checks passed

  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,973 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90

  • 3 pages without a meta description

    /shop/tv-entertainment/televisions/led, /shop/tv-entertainment/televisions/mini-led and /shop/tv-entertainment/televisions/oled have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    /store-locator, /shop/tv-entertainment/televisions, /shop/tv-entertainment/televisions/led, /shop/tv-entertainment/televisions/qled, /shop/tv-entertainment/televisions/mini-led and /shop/tv-entertainment/televisions/oled and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    /shop/tv-entertainment/audio and /shop/tv-entertainment/audio/audio-accessories took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    36 of 38 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67

  • No call to action on the first screen

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

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

  • No risk reducer

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

  • About 1,036 words of copy

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

3 checks passed

  • 8 calls to action

    The homepage has 8 calls to action, for example “Log in / Sign up”, “Buy 1 Take 1 & Bundle Deals” and “Shop Here”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • No consent tool detected

    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.

  • 3 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at western.com.ph, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on western.com.ph, including 18 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25