Website review, no card needed
pml-bmw.com.sg website review
Visit site (opens in a new tab)Reviewed 2 November 202644 issues · 92 checks
This review found 44 issues worth fixing on pml-bmw.com.sg, 11 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 123 ms |
| May 23, 2026 | 128 ms |
| May 30, 2026 | 129 ms |
| Jun 6, 2026 | 130 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 124 ms |
| Jun 27, 2026 | 122 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 121 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 122 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 123 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 117 ms |
| Oct 10, 2026 | 120 ms |
| Oct 17, 2026 | 115 ms |
| Oct 24, 2026 | 113 ms |
| Oct 31, 2026 | 115 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.4 s
0.8 s
1.3 s
1.7 s
2.1 s
2.5 s
2.9 s
3.3 s
Speed
Reduce unused JavaScript
2.0 s · 441 KiBAbout 441 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 281 KiB14 files are served with short cache lifetimes, so returning visitors download them again (281 KiB).
8 third-party services on the page
8 third-party services load with your homepage (cloudfront.net, Google Tag Manager and Facebook and others), adding 1.6 MB and 1.1 s of main-thread time.
Reduce unused CSS
920 ms · 121 KiBAbout 121 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 920 ms faster on a phone.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
cloudfront.net adds 276 ms
276 mscloudfront.net costs a phone 276 ms of main-thread work and 585 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.
Google Tag Manager adds 244 ms
244 msGoogle Tag Manager costs a phone 244 ms of main-thread work and 423 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.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,726 HTML elements
The page has 2,726 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 273 ms. During a long task the page ignores taps.
Legacy JavaScript
250 ms · 38 KiBPolyfills for old browsers add 38 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Render-blocking requests
250 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
10 KiB10 KiB could be saved by minifying JavaScript.
Improve image delivery
9 KiB2 images could be 9 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Duplicated JavaScript
4 KiB4 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 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.
Largest Contentful Paint: 13.0 s
13.0 sYour largest element takes 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 14.1 s
14.1 sThe page becomes fully interactive after 14.1 s. Good is under 3.8 s.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.9 s
2.9 sReal visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 548 ms
548 msScripts block taps and scrolling for 548 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
15 images without width and height
15 images 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-31, real Chrome visitors' tap response (inp) went from 123 ms to 115 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 115 ms
115 msReal visitors wait 115 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.5 g of CO₂ per visit
0.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.50 g of CO₂e: 59.9 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: 1.8 MB in 169 requests
1.8 MBYour homepage downloads 1.8 MB in 169 requests on a phone: scripts 1.3 MB (89), images 134 KiB (31) and fonts 131 KiB (4). 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
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
55 images without alt text
55 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 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.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 8 failed. 1 more 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.
Structured data has 2 problems
Structured data found (Organization, WebPage and WebSite) but with 2 problems, for example “WebSite: missing name”.
No social preview image
No Open Graph image (also missing: og:title, og:description), 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.
139 internal links, 42 external
The homepage links to 139 pages on pml-bmw.com.sg and 42 external pages.
5 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “The Official BMW Singapore website: BMW automobiles, services, prices, exclusive offers, technologies and all about BMW…”.
Title: 44 characters
Your title is a healthy 44 characters: “BMW Performance Motors | Official BMW Dealer”.
Canonical URL set
The canonical URL is https://www.pml-bmw.com.sg/.
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.pml-bmw.com.sg/sitemap.xml.gz.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing name, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.pml-bmw.com.sg/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 (1,093 words), so crawlers that don't run JavaScript still read it.
Other pages
6 linked pages hidden from search
https://www.pml-bmw.com.sg/deals_no_need, https://www.pml-bmw.com.sg/finance-lease, https://www.pml-bmw.com.sg/owners, https://www.pml-bmw.com.sg/digital-services-app, https://www.pml-bmw.com.sg/about-us and https://www.pml-bmw.com.sg/business-corporate are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
https://www.pml-bmw.com.sg/deals_no_need and https://www.pml-bmw.com.sg/digital-services-app all use the title “Performance Motors”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages share a meta description
https://www.pml-bmw.com.sg/deals_no_need, https://www.pml-bmw.com.sg/finance-lease and https://www.pml-bmw.com.sg/digital-services-app use the same meta description. A description written for each page earns more clicks.
12 pages without an H1
https://www.pml-bmw.com.sg/stock, https://www.pml-bmw.com.sg/models, https://www.pml-bmw.com.sg/finance-lease, https://www.pml-bmw.com.sg/owners, https://www.pml-bmw.com.sg/digital-services-app and https://www.pml-bmw.com.sg/part-accessories/bmw-accessories-hub and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 85 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://www.pml-bmw.com.sg/.
54 small tap targets
54 of 106 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are 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 “Access to XMLHttpRequest at 'https://d35wmn7bemzfye.cloudfront.net/0a967c4bd87e19bc37c1a6cf033339551cc926a9/1785851038/…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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
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: 52 customer or partner logos. 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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 693 words of copy
The homepage carries about 693 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Online” and “Buy Online”.
14 calls to action
The homepage has 14 calls to action, for example “Shop Online”, “Contact” and “Call”.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Osano
A consent management tool (Osano) loads with the page.
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 pml-bmw.com.sg, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- 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 44 issues on pml-bmw.com.sg, including 20 speed issues, 4 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.