Website review, no card needed
sgxgroup.com website review
Visit site (opens in a new tab)Reviewed 18 November 202636 issues · 72 checks
This review found 36 issues worth fixing on sgxgroup.com, 11 of them high impact, across 72 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 5.4 s |
| Jun 6, 2026 | 5.4 s |
| Jun 13, 2026 | 5.5 s |
| Jun 20, 2026 | 5.5 s |
| Jun 27, 2026 | 5.6 s |
| Jul 4, 2026 | 5.6 s |
| Jul 11, 2026 | 5.6 s |
| Jul 18, 2026 | 5.6 s |
| Jul 25, 2026 | 5.5 s |
| Aug 1, 2026 | 5.4 s |
| Aug 8, 2026 | 5.5 s |
| Aug 15, 2026 | 5.3 s |
| Aug 22, 2026 | 5.3 s |
| Aug 29, 2026 | 5.3 s |
| Sep 5, 2026 | 5.2 s |
| Sep 12, 2026 | 5.5 s |
| Sep 19, 2026 | 5.5 s |
| Sep 26, 2026 | 5.3 s |
| Oct 3, 2026 | 5.2 s |
| Oct 10, 2026 | 5.1 s |
| Oct 17, 2026 | 5.1 s |
| Oct 24, 2026 | 5.2 s |
| Oct 31, 2026 | 5.2 s |
| Nov 7, 2026 | 5.2 s |
| Nov 14, 2026 | 5.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 101 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 119 ms |
| Jun 20, 2026 | 117 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 107 ms |
| Jul 11, 2026 | 101 ms |
| Jul 18, 2026 | 101 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 100 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 99 ms |
| Aug 22, 2026 | 101 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 100 ms |
| Sep 12, 2026 | 94 ms |
| Sep 19, 2026 | 92 ms |
| Sep 26, 2026 | 92 ms |
| Oct 3, 2026 | 89 ms |
| Oct 10, 2026 | 92 ms |
| Oct 17, 2026 | 94 ms |
| Oct 24, 2026 | 97 ms |
| Oct 31, 2026 | 97 ms |
| Nov 7, 2026 | 91 ms |
| Nov 14, 2026 | 91 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.7 s
1.5 s
2.2 s
3.0 s
3.7 s
4.5 s
5.2 s
6.0 s
Speed
Reduce unused JavaScript
2.7 s · 471 KiBAbout 471 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Improve image delivery
4.7 MB21 images could be 4.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
400 ms · 2.4 MB38 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and JSDelivr CDN and others), adding 7.4 MB and 319 ms of main-thread time.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
sgx.com adds 0 ms
0 mssgx.com costs a phone 0 ms of main-thread work and 6.1 MB 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
350 ms · 29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 350 ms faster on a phone.
Render-blocking requests
350 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 350 ms.
Google Tag Manager adds 199 ms
199 msGoogle Tag Manager costs a phone 199 ms of main-thread work and 294 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.
JSDelivr CDN adds 0 ms
0 msJSDelivr CDN costs a phone 0 ms of main-thread work and 618 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.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 122 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 418 ms of it running JavaScript. That is comfortably low.
Server response: 18 ms
18 msYour server sent the HTML in 18 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.6 s
5.6 sReal visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 13.5 s
13.5 sYour largest element takes 13.5 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 (5.6 s).
Speed Index: 11.4 s
11.4 sVisually, the page fills in at 11.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.7 s
13.7 sThe page becomes fully interactive after 13.7 s. Good is under 3.8 s.
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.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 5.4 s to 5.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 105 ms
105 msReal visitors wait 105 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 101 ms to 91 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 158 ms
158 msScripts block the page for only 158 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.039
0.039The layout barely moves while loading (CLS 0.039, good is under 0.1).
First Contentful Paint: 1.0 s
1.0 sThe first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 8.5 MB in 57 requests
8.5 MBYour homepage downloads 8.5 MB in 57 requests on a phone: images 6.9 MB (33), scripts 927 KiB (8) and fonts 629 KiB (5). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
6fcb4fbf7f8a060191bc.png weighs 489 KiB. On a phone connection a single image that size takes seconds.
5 images in older formats
5 images (733 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 2.4 g of CO₂ per visit
2.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.42 g of CO₂e: 290.6 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
23 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 24 WCAG 2.2 A/AA and best-practice rules on the phone render: 23 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (9 characters)
Your title is only 9 characters: “SGX Group”. 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.
Only 1 internal link
The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
5 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “SGX Group is Asia's leading and trusted securities and derivatives market infrastructure. Learn more about SGX Group an…”.
Canonical URL set
The canonical URL is https://www.sgxgroup.com/.
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.sgxgroup.com/sitemap.xml.
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.sgxgroup.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.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Loading the script 'https://static.hotjar.com/c/hotjar-5300268.js?sv=7' violates the following Content Security Policy …”.
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 (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 74 words
The homepage has only about 74 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.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact us”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
5 other companies contacted
Loading the homepage contacts 5 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 sgxgroup.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Akamai
Company
- Headquarters
- Singapore
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on sgxgroup.com, including 18 speed issues, 5 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.