Website review, no card needed
viva.com.ph website review
Visit site (opens in a new tab)Reviewed 7 November 202619 issues · 69 checks
This review found 19 issues worth fixing on viva.com.ph, 5 of them high impact, across 69 checks. The most urgent: fails Core Web Vitals for real visitors. 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.9 s |
| May 23, 2026 | 5.0 s |
| May 30, 2026 | 5.1 s |
| Jun 6, 2026 | 5.1 s |
| Jun 13, 2026 | 5.2 s |
| Jun 20, 2026 | 5.2 s |
| Jun 27, 2026 | 5.2 s |
| Jul 4, 2026 | 5.3 s |
| Jul 18, 2026 | 5.2 s |
| Jul 25, 2026 | 5.3 s |
| Aug 1, 2026 | 5.4 s |
| Aug 8, 2026 | 5.4 s |
| Aug 15, 2026 | 5.4 s |
| Aug 22, 2026 | 5.4 s |
| Aug 29, 2026 | 5.4 s |
| Sep 5, 2026 | 5.4 s |
| Sep 12, 2026 | 5.5 s |
| Sep 19, 2026 | 5.5 s |
| Sep 26, 2026 | 5.6 s |
| Oct 3, 2026 | 5.6 s |
| Oct 10, 2026 | 5.6 s |
| Oct 17, 2026 | 5.6 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 | 132 ms |
| May 23, 2026 | 135 ms |
| May 30, 2026 | 134 ms |
| Jun 6, 2026 | 127 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 134 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 134 ms |
| Aug 8, 2026 | 135 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 141 ms |
| Aug 29, 2026 | 139 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 136 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 139 ms |
| Oct 10, 2026 | 139 ms |
| Oct 17, 2026 | 143 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 149 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
Speed
Reduce unused JavaScript
150 ms · 45 KiBAbout 45 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
6 KiB1 file is served with short cache lifetimes, so returning visitors download them again (6 KiB).
1 third-party service on the page
1 third-party service load with your homepage (Amazon Web Services), adding 6 KiB and 0 ms of main-thread time.
3 checks passed
Mobile performance score: 94
94/100Your mobile performance score is 94. That is in Google's “good” band (90 and up).
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 165 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 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: 5.8 s
5.8 sReal visitors wait 5.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.23
0.23For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 2.9 s
2.9 sYour largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “logo”. Most of its time is resource load duration (1.3 s).
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 132 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.9 s to 5.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Speed Index: 3.1 s
3.1 sVisually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Time to Interactive: 2.9 s
2.9 sThe page is fully interactive after 2.9 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.09 g of CO₂ per visit
0.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.09 g of CO₂e: 10.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 321 KiB in 19 requests
321 KiBYour homepage downloads 321 KiB in 19 requests on a phone: scripts 235 KiB (11), fonts 57 KiB (3) and stylesheets 16 KiB (2). That is a lean page.
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
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (4 characters)
Your title is only 4 characters: “Home”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No XML sitemap
No XML sitemap at http://localhost:3000/sitemap.xml, so Google discovers your pages only by following links.
61 internal links, 0 external
The homepage links to 61 pages on viva.com.ph and 0 external pages.
5 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Viva Communications, Inc., formerly known as Viva Entertainment is a premiere multi-media company known for its classic…”.
One H1 headline
Your main headline reads: “Viva Communication Inc.”.
Canonical URL set
The canonical URL is https://viva.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.
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://viva.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.
1 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.
Other pages
10 pages share a meta description
https://viva.com.ph/entertainment/epik, https://viva.com.ph/media/radios, https://viva.com.ph/music/records, https://viva.com.ph/music/artists, https://viva.com.ph/music/records/library and https://viva.com.ph/music/news and 4 others use the same meta description. A description written for each page earns more clicks.
10 pages with very little text
https://viva.com.ph/vivamax, https://viva.com.ph/entertainment/films/coming-soon, https://viva.com.ph/media/paytvs/domestic, https://viva.com.ph/media/radios, https://viva.com.ph/music/records and https://viva.com.ph/music/artists and 4 others 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.
7 pages slow to respond
https://viva.com.ph/entertainment/films/coming-soon, https://viva.com.ph/entertainment/epik, https://viva.com.ph/media/paytvs/domestic, https://viva.com.ph/music/artists, https://viva.com.ph/music/records/library and https://viva.com.ph/music/news and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
22 small tap targets
22 of 23 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.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 52 words
The homepage has only about 52 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
1 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
Privacy and tracking
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.
1 other company contacted
Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 viva.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
- HASPcms
- Framework
- Next.js
- Hosting
- Vercel
Company
- Founded
- 1981
- Headquarters
- Quezon City
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 19 issues on viva.com.ph, including 5 speed issues, 3 SEO issues and 5 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.