Website review, no card needed
savillsph.com website review
Visit site (opens in a new tab)Reviewed 1 November 202648 issues · 97 checks
This review found 48 issues worth fixing on savillsph.com, 18 of them high impact, across 97 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 23, 2026 | 3.7 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.7 s |
| Oct 24, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 116 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 114 ms |
| Jun 27, 2026 | 126 ms |
| Jul 4, 2026 | 130 ms |
| Jul 11, 2026 | 129 ms |
| Jul 18, 2026 | 126 ms |
| Jul 25, 2026 | 115 ms |
| Aug 1, 2026 | 116 ms |
| Aug 8, 2026 | 111 ms |
| Aug 15, 2026 | 112 ms |
| Aug 22, 2026 | 112 ms |
| Aug 29, 2026 | 114 ms |
| Sep 5, 2026 | 117 ms |
| Sep 12, 2026 | 123 ms |
| Sep 19, 2026 | 123 ms |
| Sep 26, 2026 | 117 ms |
| Oct 3, 2026 | 117 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 109 ms |
| Oct 24, 2026 | 102 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
Use efficient cache lifetimes
2.3 s · 1.0 MB55 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Reduce unused JavaScript
2.1 s · 792 KiBAbout 792 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Render-blocking requests
1.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
8 third-party services on the page
8 third-party services load with your homepage (hsappstatic.net, Google Tag Manager and Hubspot and others), adding 2.1 MB and 1.5 s of main-thread time.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
hsappstatic.net adds 484 ms
484 mshsappstatic.net costs a phone 484 ms of main-thread work and 711 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.
Reduce unused CSS
410 ms · 83 KiBAbout 83 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 410 ms faster on a phone.
Google Tag Manager adds 403 ms
403 msGoogle Tag Manager costs a phone 403 ms of main-thread work and 598 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.
Hubspot adds 341 ms
341 msHubspot costs a phone 341 ms of main-thread work and 541 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 316 ms. During a long task the page ignores taps.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
218 KiB4 images could be 218 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
100 ms · 37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Minify CSS
110 ms · 7 KiB7 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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 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 FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.1 s
2.1 sReal visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 9.6 s
9.6 sYour largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 20.0 s
20.0 sThe page becomes fully interactive after 20.0 s. Good is under 3.8 s.
Real-user LCP: 3.5 s
3.5 sReal visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.14
0.14For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.
54 images without width and height
54 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 555 ms
555 msScripts block taps and scrolling for 555 ms in total while the page loads. Good is under 200 ms.
Speed Index: 5.1 s
5.1 sVisually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.112
0.112The layout shifts by 0.112 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 116 ms to 102 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.7 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user INP: 107 ms
107 msReal visitors wait 107 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 3.2 MB in 118 requests
3.2 MBYour homepage downloads 3.2 MB in 118 requests on a phone: scripts 2.0 MB (43), images 793 KiB (39) and fonts 175 KiB (3). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
10 KiB1 image is downloaded at several times the size a phone draws it, for example pioneer-house-bgc.webp at 600 px wide, shown at 182 px. Resized copies would save about 10 KiB.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 107.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
Unlabelled dropdowns
3 dropdowns have no label.
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.
37 text elements with low contrast
37 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Positive tabindex
8 elements have a tabindex above 0, which scrambles the keyboard order.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate 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.
13 form fields without a label
13 form fields have no label, so screen readers announce an empty box and autofill guesses.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 63 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 10 failed. 3 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.
85 internal links, 5 external
The homepage links to 85 pages on savillsph.com and 5 external pages.
7 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Savills Philippines is the trusted full service real estate solutions provider in the Philippines. Discover more about …”.
Title: 53 characters
Your title is a healthy 53 characters: “Savills Philippines | Commercial Real Estate Services”.
Canonical URL set
The canonical URL is https://savillsph.com/.
Structured data in place
Structured data found: Organization 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://savillsph.com/sitemap.xml.
AI search readiness
Opted out of AI training for 1 crawler
robots.txt blocks Applebot-Extended, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
4 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,106 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://savillsph.com/llms.txt (3 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://savillsph.com/services/research-and-consultancy, whose canonical is https://savillsph.com/services/research-consultancy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
6 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
Every page has a meta description
All 13 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 13 pages that loaded have a <title>.
Best practices
3 broken images
3 images failed to load on a phone, for example https://savillsph.com/media/668062/aes.webp.
6 small tap targets
6 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
7 distorted images
7 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 49 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
A 10-field form
Your longest form asks for 10 fields (0 required). Every extra field lowers completion.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 996 words of copy
The homepage carries about 996 words of visible text.
5 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact Us”, “Inquire Now” and “Download the report”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity, HubSpot and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager 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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
13 other companies contacted
Loading the homepage contacts 13 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 savillsph.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on savillsph.com, including 23 speed issues, 1 SEO issue 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.