Website review, no card needed
generika.com.ph website review
Visit site (opens in a new tab)Reviewed 26 October 202642 issues · 83 checks
This review found 42 issues worth fixing on generika.com.ph, 17 of them high impact, across 83 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.9 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 184 ms |
| May 16, 2026 | 183 ms |
| May 23, 2026 | 191 ms |
| May 30, 2026 | 206 ms |
| Jun 6, 2026 | 212 ms |
| Jun 13, 2026 | 217 ms |
| Jun 20, 2026 | 222 ms |
| Jun 27, 2026 | 204 ms |
| Jul 4, 2026 | 206 ms |
| Jul 11, 2026 | 203 ms |
| Jul 18, 2026 | 189 ms |
| Jul 25, 2026 | 201 ms |
| Aug 1, 2026 | 193 ms |
| Aug 8, 2026 | 197 ms |
| Aug 15, 2026 | 197 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 201 ms |
| Sep 5, 2026 | 200 ms |
| Sep 12, 2026 | 207 ms |
| Sep 19, 2026 | 205 ms |
| Sep 26, 2026 | 196 ms |
| Oct 3, 2026 | 198 ms |
| Oct 10, 2026 | 192 ms |
| Oct 17, 2026 | 192 ms |
| Oct 24, 2026 | 208 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
0.5 s
1.1 s
1.6 s
2.2 s
2.7 s
3.2 s
3.8 s
4.3 s
Speed
Use efficient cache lifetimes
2.9 s · 8.1 MB127 files are served with short cache lifetimes, so returning visitors download them again (8.1 MB).
Improve image delivery
1.9 s · 5.1 MB13 images could be 5.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.9 s faster on a phone.
Render-blocking requests
4.2 s45 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Reduce unused JavaScript
1.5 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Google Tag Manager adds 1.8 s
1.8 sGoogle Tag Manager costs a phone 1.8 s of main-thread work and 1.7 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.
Mobile performance score: 38
38/100Your mobile performance score is 38 (desktop: 26). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 2.0 MB and 2.1 s of main-thread time.
Font display
900 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 900 ms).
Reduce unused CSS
300 ms · 48 KiBAbout 48 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.
Facebook adds 280 ms
280 msFacebook costs a phone 280 ms of main-thread work and 253 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 on the main thread
20 long tasks block the main thread while loading, the longest for 247 ms. During a long task the page ignores taps.
Legacy JavaScript
46 KiBPolyfills for old browsers add 46 KiB JavaScript that modern phones do not need.
Minify JavaScript
15 KiB15 KiB could be saved by minifying JavaScript.
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
Server response: 157 ms
157 msYour server sent the HTML in 157 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.
Time to Interactive: 36.1 s
36.1 sThe page becomes fully interactive after 36.1 s. Good is under 3.8 s.
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mobile”.
Speed Index: 9.0 s
9.0 sVisually, the page fills in at 9.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 212 ms
212 msReal visitors wait 212 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 973 ms
973 msReal visitors wait 973 ms for your server to start answering (75th percentile). Good is under 800 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 184 ms to 208 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.9 MB in 175 requests
9.9 MBYour homepage downloads 9.9 MB in 175 requests on a phone: images 6.6 MB (30), scripts 2.3 MB (62) and fonts 757 KiB (5). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
generika-drugstore-logo-768x313.png 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).
7 images in older formats
7 images (760 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.
1 image far larger than shown
11 KiB1 image is downloaded at several times the size a phone draws it, for example unnamed-9.png at 512 px wide, shown at 164 px. Resized copies would save about 11 KiB.
1 image below the first screen load straight away
1 image further down the page (69 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.8 g of CO₂ per visit
2.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.80 g of CO₂e: 336.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 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)
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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
68 internal links, 15 external
The homepage links to 68 pages on generika.com.ph and 15 external pages.
7 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Affordable and quality generic medicines. Ang drugstore na may ginhawa sa bulsa, sa plus services, at sa katuwang. Visi…”.
Title: 53 characters
Your title is a healthy 53 characters: “GENERIKA DRUGSTORE - GINHAWANG GENERIKA PARA SA LAHAT”.
Canonical URL set
The canonical URL is https://www.generika.com.ph/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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://www.generika.com.ph/sitemap.xml.
AI search readiness
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 description; sameAs (social profiles) and contact details would complete it.
llms.txt published
The site publishes https://www.generika.com.ph/llms.txt (86 KiB, 911 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.generika.com.ph/privacy-policy is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.generika.com.ph/careers has no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://www.generika.com.ph/promos-and-discounts, https://www.generika.com.ph/philhealth-gamot, https://www.generika.com.ph/dswd-aics, https://www.generika.com.ph/privacy-policy, https://www.generika.com.ph/product-and-services and https://www.generika.com.ph/plus-services and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.generika.com.ph/medical-mission, https://www.generika.com.ph/new-store-openings and https://www.generika.com.ph/philhealth-gamot took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.
4 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 a title
All 15 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Thin social proof
Social proof on the homepage: 31 testimonial or review blocks. 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.
Only about 102 words
The homepage has only about 102 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Contact Us”, “SHOP NOW” and “Shop Now”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
12 other companies contacted
Loading the homepage contacts 12 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 generika.com.ph, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Framework
- React
- Analytics
- Google Analytics | Google Tag Manager
Company
- Founded
- 2004
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on generika.com.ph, including 22 speed issues, 2 SEO issues and 4 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.