Website review, no card needed
ngochewhong.com website review
Visit site (opens in a new tab)Reviewed 24 October 202640 issues · 79 checks
This review found 40 issues worth fixing on ngochewhong.com, 19 of them high impact, across 79 checks. The most urgent: render-blocking requests. 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
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.5 s |
| May 9, 2026 | 4.9 s |
| May 16, 2026 | 4.6 s |
| May 23, 2026 | 4.5 s |
| May 30, 2026 | 4.0 s |
| Jun 6, 2026 | 6.0 s |
| Jun 13, 2026 | 6.3 s |
| Jun 20, 2026 | 6.2 s |
| Jun 27, 2026 | 5.7 s |
| Jul 4, 2026 | 5.2 s |
| Jul 11, 2026 | 5.0 s |
| Jul 18, 2026 | 5.2 s |
| Jul 25, 2026 | 5.3 s |
| Aug 1, 2026 | 5.0 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.5 s |
| Aug 22, 2026 | 4.3 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 5.6 s |
| Sep 19, 2026 | 6.0 s |
| Sep 26, 2026 | 5.8 s |
| Oct 3, 2026 | 5.2 s |
| Oct 10, 2026 | 4.7 s |
| Oct 17, 2026 | 5.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 112 ms |
| May 16, 2026 | 113 ms |
| May 23, 2026 | 107 ms |
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 117 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 143 ms |
| Jun 27, 2026 | 142 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 131 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 114 ms |
| Aug 1, 2026 | 114 ms |
| Aug 8, 2026 | 110 ms |
| Aug 15, 2026 | 118 ms |
| Aug 29, 2026 | 102 ms |
| Sep 5, 2026 | 106 ms |
| Sep 12, 2026 | 107 ms |
| Sep 19, 2026 | 115 ms |
| Sep 26, 2026 | 126 ms |
| Oct 3, 2026 | 127 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 133 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.7 s
3.5 s
5.2 s
6.9 s
8.7 s
10.4 s
12.1 s
13.9 s
Speed
Render-blocking requests
5.5 s39 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.5 s.
Improve image delivery
3.2 s · 1.6 MB13 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.2 s faster on a phone.
Use efficient cache lifetimes
2.5 s · 805 KiB79 files are served with short cache lifetimes, so returning visitors download them again (805 KiB).
Font display
2.2 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.2 s).
Reduce unused JavaScript
1.1 s · 206 KiBAbout 206 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 47
47/100Your mobile performance score is 47 (desktop: 61). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
900 ms · 186 KiBAbout 186 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 220 KiB and 136 ms of main-thread time.
Minify CSS
150 ms · 3 KiB3 KiB could be saved by minifying CSS.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 133 ms. During a long task the page ignores taps.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
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 LCP: 5.7 s
5.7 sReal visitors wait 5.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.1 s
4.1 sReal visitors see the first content after 4.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.5 s
2.5 sReal visitors wait 2.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 13.4 s
13.4 sYour largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (9.8 s).
Speed Index: 19.8 s
19.8 sVisually, the page fills in at 19.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.5 s
13.5 sThe page becomes fully interactive after 13.5 s. Good is under 3.8 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.176
0.176The layout shifts by 0.176 while loading, so content jumps under the reader's thumb. Good is under 0.1.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 112 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.5 s to 5.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 123 ms
123 msReal visitors wait 123 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 162 ms
162 msScripts block the page for only 162 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.8 MB in 88 requests
4.8 MBYour homepage downloads 4.8 MB in 88 requests on a phone: images 3.7 MB (26), scripts 560 KiB (22) and stylesheets 267 KiB (28). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (116 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.
About 1.4 g of CO₂ per visit
1.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.36 g of CO₂e: 162.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Orphan list items
Some list items are not inside a list.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
ARIA input fields do not have accessible names
ARIA input fields do not have accessible names (2 elements).
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 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 meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.ngochewhong.com/sitemap.xml, so Google discovers your pages only by following links.
14 links crawlers can't follow
14 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
95 internal links, 7 external
The homepage links to 95 pages on ngochewhong.com and 7 external pages.
3 checks passed
Title: 45 characters
Your title is a healthy 45 characters: “Ngo Chew Hong – Your Global Strategic Partner”.
Canonical URL set
The canonical URL is https://www.ngochewhong.com/.
robots.txt in place
robots.txt is in place.
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.ngochewhong.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.
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
15 pages without a meta description
https://www.ngochewhong.com/about-us, https://www.ngochewhong.com/our-brands, https://www.ngochewhong.com/oki, https://www.ngochewhong.com/turkey, https://www.ngochewhong.com/mona and https://www.ngochewhong.com/carolin and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.ngochewhong.com/about-us, https://www.ngochewhong.com/our-brands, https://www.ngochewhong.com/oki, https://www.ngochewhong.com/turkey, https://www.ngochewhong.com/mona and https://www.ngochewhong.com/carolin and 9 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 43 found) and read each the way a search engine does.
5 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.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
10 of 10 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. 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 49 words
The homepage has only about 49 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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US”.
2 calls to action
The homepage has 2 calls to action, for example “CONTACT US”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
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.
2 other companies contacted
Loading the homepage contacts 2 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 ngochewhong.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on ngochewhong.com, including 19 speed issues, 6 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.