Website review, no card needed
dextrus.in website review
Visit site (opens in a new tab)Reviewed 6 November 202630 issues · 82 checks
This review found 30 issues worth fixing on dextrus.in, 11 of them high impact, across 82 checks. The most urgent: reduce initial server response time. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 8.2 s |
| May 23, 2026 | 8.4 s |
| May 30, 2026 | 8.5 s |
| Jun 6, 2026 | 8.4 s |
| Jun 13, 2026 | 8.3 s |
| Jun 20, 2026 | 7.4 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 378 ms |
| May 23, 2026 | 428 ms |
| May 30, 2026 | 452 ms |
| Jun 6, 2026 | 439 ms |
| Jun 13, 2026 | 433 ms |
| Jun 20, 2026 | 363 ms |
| Jun 27, 2026 | 209 ms |
| Jul 4, 2026 | 194 ms |
| Jul 11, 2026 | 185 ms |
| Jul 18, 2026 | 193 ms |
| Jul 25, 2026 | 185 ms |
| Aug 1, 2026 | 192 ms |
| Aug 8, 2026 | 206 ms |
| Aug 15, 2026 | 200 ms |
| Aug 22, 2026 | 206 ms |
| Aug 29, 2026 | 200 ms |
| Sep 5, 2026 | 205 ms |
| Sep 12, 2026 | 214 ms |
| Sep 19, 2026 | 210 ms |
| Sep 26, 2026 | 221 ms |
| Oct 3, 2026 | 216 ms |
| Oct 10, 2026 | 216 ms |
| Oct 17, 2026 | 220 ms |
| Oct 24, 2026 | 203 ms |
| Oct 31, 2026 | 217 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
Speed
Reduce initial server response time
1.1 sReduce initial server response time. Google estimates savings of 1.1 s on a phone.
Document request latency
1.1 sThe HTML itself could arrive about 1.1 s sooner: redirects, a slow server response or missing compression delay everything after it.
4,536 HTML elements
The page has 4,536 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 79
79/100Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
294 KiBAbout 294 KiB of CSS is downloaded but never applied on this page.
Server response: 1.2 s
1.2 sYour server takes 1.2 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
nitrocdn.com adds 31 ms
31 msnitrocdn.com costs a phone 31 ms of main-thread work and 503 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.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, nitrocdn.com and Google Fonts and others), adding 726 KiB and 94 ms of main-thread time.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 155 ms. During a long task the page ignores taps.
Reduce unused JavaScript
67 KiBAbout 67 KiB of JavaScript is downloaded but never used on this page.
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
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 246 ms of it running JavaScript. That is comfortably low.
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 FCP: 3.5 s
3.5 sReal visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Speed Index: 5.8 s
5.8 sVisually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.6 s
3.6 sReal visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Time to Interactive: 6.3 s
6.3 sThe page becomes fully interactive after 6.3 s. Good is under 3.8 s.
Largest Contentful Paint: 3.4 s
3.4 sYour largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “An extraordinary coworking space in Mumbai, intelligently d…”. Most of its time is element render delay (2.1 s).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Tap response (INP) got 48% faster for real visitors
-48%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 378 ms to 217 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 76% faster for real visitors
-76%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 8.2 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 149 ms
149 msScripts block the page for only 149 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
About 0.5 g of CO₂ per visit
0.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.47 g of CO₂e: 56.5 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.7 MB in 79 requests
1.7 MBYour homepage downloads 1.7 MB in 79 requests on a phone: other files 676 KiB (59), HTML 299 KiB (1) and stylesheets 221 KiB (5). 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
70 text elements with low contrast
70 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.
All page content should be contained by landmarks (48 elements)
All page content should be contained by landmarks: 48 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 61 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Shared Office Space - 24 Hours Coworking Space in Mumbai | Dextrus”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
137 internal links, 13 external
The homepage links to 137 pages on dextrus.in and 13 external pages.
6 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Discover Dextrus workspace, a coworking space in Mumbai designed for teams, professionals, startups & business enterpri…”.
One H1 headline
Your main headline reads: “DEXTRUS”.
Canonical URL set
The canonical URL is https://dextrus.in/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and Place.
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://dextrus.in/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, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,290 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without an H1
https://dextrus.in/contact-us, https://dextrus.in/bkc-crescenzo, https://dextrus.in/lower-parel-peninsula-corporate-park, https://dextrus.in/one-bkc, https://dextrus.in/andheri-mint and https://dextrus.in/fixed-desks and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages slow to respond
https://dextrus.in/contact-us, https://dextrus.in/lower-parel-peninsula-corporate-park, https://dextrus.in/one-bkc, https://dextrus.in/fixed-desks, https://dextrus.in/membership-plans and https://dextrus.in/daily-virtual-plans took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 37 found) and read each the way a search engine does.
6 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.
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
6 small tap targets
6 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
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.
A 8-field form
Your longest form asks for 8 fields (4 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 534 words of copy
The homepage carries about 534 words of visible text.
5 checks passed
7 calls to action
The homepage has 7 calls to action, for example “CONTACT US”, “Contact Us” and “Book a Meeting Room”.
Social proof on the page
Social proof on the homepage: 32 testimonial or review blocks, 1 customer or partner logo and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Microsoft Clarity.
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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads 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.
4 cookies set on arrival
4Opening the homepage sets 4 cookies, 2 of them by other companies (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.
6 other companies contacted
Loading the homepage contacts 6 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 dextrus.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- DigitalOcean
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on dextrus.in, including 15 speed issues, 2 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.