Website review, no card needed
aertsen.in website review
Visit site (opens in a new tab)Reviewed 19 October 202644 issues · 85 checks
This review found 44 issues worth fixing on aertsen.in, 19 of them high impact, across 85 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
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 6.3 s |
| May 2, 2026 | 5.4 s |
| May 9, 2026 | 4.2 s |
| May 16, 2026 | 3.7 s |
| May 23, 2026 | 3.9 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 4.2 s |
| Aug 1, 2026 | 4.4 s |
| Aug 8, 2026 | 4.6 s |
| Aug 15, 2026 | 4.5 s |
| Aug 22, 2026 | 4.5 s |
| Aug 29, 2026 | 4.6 s |
| Sep 5, 2026 | 4.4 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 105 ms |
| May 2, 2026 | 100 ms |
| May 9, 2026 | 102 ms |
| May 16, 2026 | 102 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 111 ms |
| Jun 13, 2026 | 117 ms |
| Jun 20, 2026 | 111 ms |
| Jun 27, 2026 | 120 ms |
| Jul 4, 2026 | 125 ms |
| Jul 11, 2026 | 126 ms |
| Jul 18, 2026 | 134 ms |
| Jul 25, 2026 | 126 ms |
| Aug 1, 2026 | 118 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 134 ms |
| Aug 22, 2026 | 136 ms |
| Aug 29, 2026 | 138 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 131 ms |
| Sep 19, 2026 | 131 ms |
| Sep 26, 2026 | 135 ms |
| Oct 3, 2026 | 131 ms |
| Oct 10, 2026 | 138 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 unused JavaScript
7.4 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.4 s faster on a phone.
Render-blocking requests
1.8 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Google CDN adds 1.1 s
1.1 sGoogle CDN costs a phone 1.1 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 36
36/100Your mobile performance score is 36 (desktop: 39). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
900 ms · 6.4 MB28 files are served with short cache lifetimes, so returning visitors download them again (6.4 MB).
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 2.5 MB and 2.3 s of main-thread time.
Improve image delivery
150 ms · 568 KiB12 images could be 568 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Google Tag Manager adds 647 ms
647 msGoogle Tag Manager costs a phone 647 ms of main-thread work and 511 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 454 ms. During a long task the page ignores taps.
Facebook adds 348 ms
348 msFacebook costs a phone 348 ms of main-thread work and 265 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.
YouTube adds 18 ms
18 msYouTube costs a phone 18 ms of main-thread work and 444 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.
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 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.4 s
5.4 sReal visitors wait 5.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.
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: 19.6 s
19.6 sYour largest element takes 19.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our website uses cookies to give you the best and most rele…”.
Time to Interactive: 19.9 s
19.9 sThe page becomes fully interactive after 19.9 s. Good is under 3.8 s.
Speed Index: 10.6 s
10.6 sVisually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 105 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 6.3 s to 4.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 17.5 MB in 77 requests
17.5 MBYour homepage downloads 17.5 MB in 77 requests on a phone: media 13.9 MB (3), scripts 2.0 MB (24) and images 1.0 MB (19). Under 2 MB keeps phones on slow connections fast.
4 images far larger than shown
526 KiB4 images are downloaded at several times the size a phone draws them, for example house-interior-designers-in-hyderabad-5a7bd19a.jpg at 2,500 px wide, shown at 310 px. Resized copies would save about 526 KiB.
4 images in older formats
4 images (904 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.
4 images below the first screen load straight away
4 images further down the page (904 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.0 g of CO₂ per visit
4.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.97 g of CO₂e: 596.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
13 buttons without a name
13 buttons have no accessible name, so screen readers announce just “button”.
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (43 elements)
All page content should be contained by landmarks: 43 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
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.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 41 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No robots.txt
There is no robots.txt at aertsen.in/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
63 internal links, 12 external
The homepage links to 63 pages on aertsen.in and 12 external pages.
5 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “Aertsen Living offers the best home interiors in Hyderabad — modular kitchens, full home interiors & 10-year warranty. …”.
Title: 49 characters
Your title is a healthy 49 characters: “Best Home Interiors in Hyderabad - Aertsen Living”.
Structured data in place
Structured data found: FAQPage.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://aertsen.in/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://aertsen.in/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.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,366 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages share a title
https://aertsen.in/aertsen-diary, https://aertsen.in/projects/soft-curves-and-golden-details, https://aertsen.in/projects/warm-tones-and-elegant-details, https://aertsen.in/projects/the-everyday-made-beautiful and https://aertsen.in/projects/where-gold-meets-timeless-living all use the title “Home Interior Design Portfolio | Aertsen Living”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages share a meta description
https://aertsen.in/aertsen-diary, https://aertsen.in/projects/soft-curves-and-golden-details, https://aertsen.in/projects/warm-tones-and-elegant-details, https://aertsen.in/projects/the-everyday-made-beautiful and https://aertsen.in/projects/where-gold-meets-timeless-living use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 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.
Every page has an H1
Each page we checked has a main headline.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
24 of 25 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 10-field form
Your longest form asks for 10 fields (9 required). Every extra field lowers completion.
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 1,671 words of copy
The homepage carries about 1,671 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
6 calls to action
The homepage has 6 calls to action, for example “Contact”, “Book Free Consultation” and “Call 040-4189-5555”.
Social proof on the page
Social proof on the homepage: 6 testimonial or review blocks, a star rating and “1500 + Happy Customers”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 5 phone links and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
20 other companies contacted
Loading the homepage contacts 20 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 aertsen.in, 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
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on aertsen.in, including 23 speed issues, 3 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.