Website review, no card needed
cdsg.com.mm website review
Visit site (opens in a new tab)Reviewed 17 November 202629 issues · 43 checks
This review found 29 issues worth fixing on cdsg.com.mm, 10 of them high impact, across 43 checks. The most urgent: improve image delivery. 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
64DNot ranked: the homepage didn't load normally in this review.
One score from every part of this review. How it works
Speed
Improve image delivery
1.5 s · 1.5 MB7 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.
Render-blocking requests
1.5 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 77
77/100Your mobile performance score is 77. Pages that score under 90 lose visitors before the first paint.
Font display
900 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 900 ms).
Reduce unused JavaScript
548 KiBAbout 548 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
440 ms · 98 KiBAbout 98 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 440 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.1 MB and 401 ms of main-thread time.
Google CDN adds 263 ms
263 msGoogle CDN costs a phone 263 ms of main-thread work and 742 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.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 90 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
18 KiB4 files are served with short cache lifetimes, so returning visitors download them again (18 KiB).
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 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.
Time to Interactive: 15.0 s
15.0 sThe page becomes fully interactive after 15.0 s. Good is under 3.8 s.
Speed Index: 10.1 s
10.1 sVisually, the page fills in at 10.1 s (Speed Index). Good is under 3.4 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.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.9 s
3.9 sYour largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Capital Diamond Star Group Limited (“CDSG”) is one of Myanm…”. Most of its time is element render delay (3.4 s).
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.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 38 ms
38 msScripts block the page for only 38 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 8.3 MB in 78 requests
8.3 MBYour homepage downloads 8.3 MB in 78 requests on a phone: images 6.4 MB (25), scripts 1.2 MB (22) and other files 358 KiB (7). Under 2 MB keeps phones on slow connections fast.
About 2.4 g of CO₂ per visit
2.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.35 g of CO₂e: 282.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
[role]s are not contained by their required parent element
[role]s are not contained by their required parent element (6 elements).
Image elements do not have [alt] attributes
Image elements do not have [alt] attributes (1 element).
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Links do not have a discernible name
Links do not have a discernible name (6 elements).
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 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.
Heading elements are not in a sequentially-descending order
Heading elements are not in a sequentially-descending order (3 elements).
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
SEO
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Invalid hreflang
Your hreflang tags are invalid, so Google may show the wrong language version.
Best practices
2 console errors
2 errors were logged to the browser console during Google's test (“requestStorageAccess: Permission denied.”).
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Content and conversion
Homepage could not be loaded
We could not load https://cdsg.com.mm from our server, so the homepage checks are missing. If the site is up, it may block automated visitors.
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 cdsg.com.mm, 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
- Hosting
- Whg Sgp
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on cdsg.com.mm, including 17 speed issues, 2 SEO issues and 1 conversion gap. 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.