Website review, no card needed
sonarplatform.com website review
Visit site (opens in a new tab)Reviewed 21 October 202620 issues · 73 checks
This review found 20 issues worth fixing on sonarplatform.com, 8 of them high impact, across 73 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.7 s |
| May 9, 2026 | 3.7 s |
| May 16, 2026 | 3.8 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.7 s |
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.9 s
1.9 s
2.8 s
3.8 s
4.7 s
5.6 s
6.6 s
7.5 s
Speed
Render-blocking requests
14.8 s47 files block the first paint until they finish downloading. Deferring or inlining them could save about 14.8 s.
Reduce unused CSS
12.3 s · 2.2 MBAbout 2.2 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 12.3 s faster on a phone.
Improve image delivery
1.4 s · 280 KiB1 image could be 280 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 62). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
350 ms · 188 KiB3 files are served with short cache lifetimes, so returning visitors download them again (188 KiB).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 59 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 42 KiB and 0 ms of main-thread time.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 41 ms of it running JavaScript. That is comfortably low.
Server response: 220 ms
220 msYour server sent the HTML in 220 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 15.6 s
15.6 sThe first text or image appears after 15.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 19.1 s
19.1 sYour largest element takes 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Integrated Media Intelligence Our next gen integrated platf…”.
Speed Index: 15.6 s
15.6 sVisually, the page fills in at 15.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 19.1 s
19.1 sThe page becomes fully interactive after 19.1 s. Good is under 3.8 s.
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.7 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0.012
0.012The layout barely moves while loading (CLS 0.012, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.3 MB in 64 requests
3.3 MBYour homepage downloads 3.3 MB in 64 requests on a phone: stylesheets 2.4 MB (48), images 654 KiB (10) and fonts 225 KiB (4). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 29 images in the HTML carry an alt attribute.
27 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 27 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
33 internal links, 5 external
The homepage links to 33 pages on sonarplatform.com and 5 external pages.
8 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Delivering integrated media intelligence across social media, traditional media, and e-commerce across multiple industr…”.
One H1 headline
Your main headline reads: “dataxet:sonar is part of the Dataxet group.”.
Title: 64 characters
Your title is a healthy 64 characters: “The Leading Social Media Listening Tools Indonesia Dataxet:Sonar”.
Canonical URL set
The canonical URL is https://sonarplatform.com/.
Structured data in place
Structured data found: Article, Corporation, ImageObject, Organization and Person.
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://sonarplatform.com/sitemap_index.xml.
AI search readiness
3 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
llms.txt published
The site publishes https://sonarplatform.com/llms.txt (40 KiB, 101 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
2 pages without an H1
https://sonarplatform.com/contact-us and https://sonarplatform.com/dtx360 have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://sonarplatform.com/about-us took over 3 s to send its HTML from our server.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 8 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 8 pages that loaded have a meta description.
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 8 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
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.
Only about 95 words
The homepage has only about 95 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US” and “Request Demo”.
5 calls to action
The homepage has 5 calls to action, for example “Contact Us”, “Request Demo” and “Get in touch”.
Social proof on the page
Social proof on the homepage: 79 testimonial or review blocks and 1 customer or partner logo.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 sonarplatform.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on sonarplatform.com, including 9 speed issues, 1 SEO issue and 2 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.