wilcon.com.ph website review

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

100 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).

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

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

About 285 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

7 third-party services load with your homepage (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 40.1 MB and 620 ms of main-thread time.

Amazon Web Services costs a phone 0 ms of main-thread work and 38.9 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.

YouTube costs a phone 478 ms of main-thread work and 987 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.

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

4 KiB could be saved by minifying CSS.

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

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

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

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.

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

Your largest element takes 48.6 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 59.0 s. Good is under 3.8 s.

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

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

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

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

17 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-31, real Chrome visitors' tap response (inp) went from 118 ms to 111 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 2.6 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

12 images weigh 67.0 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 42.0 MB in 158 requests on a phone: images 39.8 MB (52), scripts 1.5 MB (59) and fonts 320 KiB (5). Under 2 MB keeps phones on slow connections fast.

39 images (70.6 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.

WILCON-ONLINE-SHOP-NOW-OPEN-500x550px-1-768x845.jpg 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).

3 images are downloaded at several times the size a phone draws them, for example MY-WILCON-OWWA-PLUS-REWARDS-CORP-BANNER-MOBILE-2.jpg at 1,200 px wide, shown at 370 px. Resized copies would save about 351 KiB.

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

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 13 characters: “Home - Wilcon”. Between 30 and 65 characters leaves room to say what you do and for whom.

No XML sitemap at https://wilcon.com.ph/sitemap_index.xml, so Google discovers your pages only by following links.

The homepage links to 144 pages on wilcon.com.ph and 57 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://wilcon.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://wilcon.com.ph/about-us, https://wilcon.com.ph/mission-vision-values, https://wilcon.com.ph/e-news, https://wilcon.com.ph/series, https://wilcon.com.ph/careers and https://wilcon.com.ph/e-magazine and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://wilcon.com.ph/e-news/2024/03/01/go-green-with-wilcon-depots-new-sustainable-shopping-bags, whose canonical is https://wilcon.com.ph/e-news/2024/03/go-green-with-wilcon-depots-new-sustainable-shopping-bags. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://wilcon.com.ph/about-us, https://wilcon.com.ph/mission-vision-values, https://wilcon.com.ph/series, https://wilcon.com.ph/careers, https://wilcon.com.ph/e-magazine and https://wilcon.com.ph/promos and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://wilcon.com.ph/promos, https://wilcon.com.ph/branches and https://wilcon.com.ph/my-wilcon-app have 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.

https://wilcon.com.ph/mywilcon-owwa took over 3 s to send its HTML from our server.

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

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

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

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

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

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

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

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

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