Website review, no card needed
pilmico.com website review
Visit site (opens in a new tab)Reviewed 2 November 202638 issues · 84 checks
This review found 38 issues worth fixing on pilmico.com, 21 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.6 s |
| May 23, 2026 | 5.5 s |
| May 30, 2026 | 5.2 s |
| Jun 6, 2026 | 5.1 s |
| Jun 13, 2026 | 5.4 s |
| Jun 20, 2026 | 5.5 s |
| Jun 27, 2026 | 5.6 s |
| Jul 4, 2026 | 5.7 s |
| Jul 11, 2026 | 5.8 s |
| Jul 18, 2026 | 5.8 s |
| Jul 25, 2026 | 5.8 s |
| Aug 1, 2026 | 5.8 s |
| Aug 8, 2026 | 5.7 s |
| Aug 15, 2026 | 5.9 s |
| Aug 22, 2026 | 6.2 s |
| Aug 29, 2026 | 6.4 s |
| Sep 5, 2026 | 6.4 s |
| Sep 12, 2026 | 6.2 s |
| Sep 19, 2026 | 5.6 s |
| Sep 26, 2026 | 5.5 s |
| Oct 3, 2026 | 5.5 s |
| Oct 10, 2026 | 5.6 s |
| Oct 17, 2026 | 5.8 s |
| Oct 24, 2026 | 5.7 s |
| Oct 31, 2026 | 5.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 228 ms |
| May 23, 2026 | 238 ms |
| May 30, 2026 | 247 ms |
| Jun 6, 2026 | 248 ms |
| Jun 13, 2026 | 240 ms |
| Jun 20, 2026 | 245 ms |
| Jun 27, 2026 | 245 ms |
| Jul 4, 2026 | 244 ms |
| Jul 11, 2026 | 247 ms |
| Jul 18, 2026 | 244 ms |
| Jul 25, 2026 | 237 ms |
| Aug 1, 2026 | 264 ms |
| Aug 8, 2026 | 260 ms |
| Aug 15, 2026 | 262 ms |
| Aug 22, 2026 | 278 ms |
| Aug 29, 2026 | 268 ms |
| Sep 5, 2026 | 274 ms |
| Sep 12, 2026 | 268 ms |
| Sep 19, 2026 | 243 ms |
| Sep 26, 2026 | 228 ms |
| Oct 3, 2026 | 228 ms |
| Oct 10, 2026 | 230 ms |
| Oct 17, 2026 | 239 ms |
| Oct 24, 2026 | 242 ms |
| Oct 31, 2026 | 248 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
How it loaded on a phone
1.2 s
2.4 s
3.7 s
4.9 s
6.1 s
7.3 s
8.5 s
9.8 s
Speed
Use efficient cache lifetimes
11.4 s · 4.5 MB39 files are served with short cache lifetimes, so returning visitors download them again (4.5 MB).
Improve image delivery
6.5 s · 2.2 MB5 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.5 s faster on a phone.
Render-blocking requests
6.2 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.2 s.
Reduce unused CSS
4.3 s · 872 KiBAbout 872 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.3 s faster on a phone.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 30
30/100Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
450 ms · 910 KiBAbout 910 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 1.3 MB and 588 ms of main-thread time.
Google Tag Manager adds 403 ms
403 msGoogle Tag Manager costs a phone 403 ms of main-thread work and 868 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 131 ms. During a long task the page ignores taps.
Legacy JavaScript
88 KiBPolyfills for old browsers add 88 KiB JavaScript that modern phones do not need.
Document request latency
58 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 770 ms of it running JavaScript. That is comfortably low.
Server response: 214 ms
214 msYour server sent the HTML in 214 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 4.5 s
4.5 sReal visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 1.06
1.06For real visitors the layout shifts by 1.06 (75th percentile). Good is under 0.1.
Real-user FCP: 3.5 s
3.5 sReal visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 15.6 s
15.6 sYour largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “products”.
Time to Interactive: 27.1 s
27.1 sThe page becomes fully interactive after 27.1 s. Good is under 3.8 s.
Speed Index: 15.0 s
15.0 sVisually, the page fills in at 15.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 6.5 s
6.5 sThe first text or image appears after 6.5 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.929
0.929The layout shifts by 0.929 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 228 ms to 248 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.6 s to 5.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 181 ms
181 msReal visitors wait 181 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 129 ms
129 msScripts block the page for only 129 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.5 MB in 69 requests
5.5 MBYour homepage downloads 5.5 MB in 69 requests on a phone: images 2.4 MB (12), scripts 1.9 MB (26) and stylesheets 924 KiB (12). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (863 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 below the first screen load straight away
3 images further down the page (584 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.56 g of CO₂e: 187.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
35 text elements with low contrast
35 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 9 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 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 H1 headlines
There are 4 <h1> headlines (“Welcome, Partner!”, “About Pilmico” and “Get In Touch”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
39 internal links, 13 external
The homepage links to 39 pages on pilmico.com and 13 external pages.
6 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Pilmico, one of the Philippines' largest Agribusiness and Food & Nutrition companies, offers top-quality agricultural c…”.
Title: 59 characters
Your title is a healthy 59 characters: “Your Partner in Agribusiness and Food & Nutrition | Pilmico”.
Canonical URL set
The canonical URL is https://www.pilmico.com/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
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://www.pilmico.com/sitemap_index.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.pilmico.com/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (393 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages without a meta description
https://www.pilmico.com/products/products-feeds/products-feeds-broiler-and-layer, https://www.pilmico.com/products/products-feeds/products-feeds-duck-and-quail, https://www.pilmico.com/products/products-feeds/products-feeds-animal-health, https://www.pilmico.com/products/products-flour/products-flour-hard-wheat-flour, https://www.pilmico.com/products/products-flour/products-flour-soft-wheat-flour and https://www.pilmico.com/products/products-flour/products-flour-specialty-flour and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages slow to respond
https://www.pilmico.com/products/products-feeds/products-feeds-swine and https://www.pilmico.com/products/products-feeds/products-feeds-pet-food took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
6 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.
Every page has an H1
Each page we checked has a main headline.
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
4 small tap targets
4 of 8 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 369 words of copy
The homepage carries about 369 words of visible text.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact”, “Contact Us” and “Subscribe Now”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot 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.
9 cookies set on arrival
9Opening the homepage sets 9 cookies (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.
25 other companies contacted
Loading the homepage contacts 25 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 pilmico.com, 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
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on pilmico.com, including 19 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.