Website review, no card needed
swapnilpatni.com website review
Visit site (opens in a new tab)Reviewed 19 October 202639 issues · 86 checks
This review found 39 issues worth fixing on swapnilpatni.com, 15 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.4 s |
| May 2, 2026 | 1.2 s |
| May 9, 2026 | 1.1 s |
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 991 ms |
| Sep 19, 2026 | 981 ms |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 994 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 155 ms |
| May 2, 2026 | 152 ms |
| May 9, 2026 | 148 ms |
| May 16, 2026 | 150 ms |
| May 23, 2026 | 152 ms |
| May 30, 2026 | 151 ms |
| Jun 6, 2026 | 148 ms |
| Jun 13, 2026 | 144 ms |
| Jun 20, 2026 | 139 ms |
| Jun 27, 2026 | 136 ms |
| Jul 4, 2026 | 135 ms |
| Jul 11, 2026 | 134 ms |
| Jul 18, 2026 | 133 ms |
| Jul 25, 2026 | 134 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 141 ms |
| Aug 15, 2026 | 143 ms |
| Aug 22, 2026 | 143 ms |
| Aug 29, 2026 | 141 ms |
| Sep 5, 2026 | 141 ms |
| Sep 12, 2026 | 141 ms |
| Sep 19, 2026 | 139 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 135 ms |
| Oct 10, 2026 | 133 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.6 s
1.2 s
1.9 s
2.5 s
3.1 s
3.7 s
4.4 s
5.0 s
Speed
Use efficient cache lifetimes
4.6 s · 2.6 MB31 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
Render-blocking requests
2.1 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Reduce unused CSS
1.5 s · 199 KiBAbout 199 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Improve image delivery
1.3 s · 253 KiB2 images could be 253 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.
Mobile performance score: 41
41/100Your mobile performance score is 41 (desktop: 62). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Font display
850 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 850 ms).
Minify CSS
150 ms · 33 KiB33 KiB could be saved by minifying CSS.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 104 ms. During a long task the page ignores taps.
Reduce unused JavaScript
32 KiBAbout 32 KiB of JavaScript is downloaded but never used on this page.
2 third-party services on the page
2 third-party services load with your homepage (Google Fonts and Cloudflare CDN), adding 244 KiB and 0 ms of main-thread time.
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: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 302 ms of it running JavaScript. That is comfortably low.
Server response: 270 ms
270 msYour server sent the HTML in 270 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.
Largest Contentful Paint: 10.1 s
10.1 sYour largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SPC Image”.
Speed Index: 8.6 s
8.6 sVisually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 10.2 s
10.2 sThe page becomes fully interactive after 10.2 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.393
0.393The layout shifts by 0.393 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.25
0.25For real visitors the layout shifts by 0.25 (75th percentile). Good is under 0.1.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 111 ms
111 msReal visitors wait 111 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 383 ms
383 msReal visitors wait 383 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 155 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 27 ms
27 msScripts block the page for only 27 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.1 MB in 71 requests
3.1 MBYour homepage downloads 3.1 MB in 71 requests on a phone: images 2.2 MB (18), fonts 412 KiB (6) and stylesheets 243 KiB (19). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
177 KiB2 images are downloaded at several times the size a phone draws them, for example WhatsApp Image 2026-06-26 at 12.31.48 PM.jpeg at 1,600 px wide, shown at 390 px. Resized copies would save about 177 KiB.
2 images in older formats
2 images (282 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 0.9 g of CO₂ per visit
0.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.87 g of CO₂e: 104.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (33 elements)
All page content should be contained by landmarks: 33 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.
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.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 36 images in the HTML carry an alt attribute.
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 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.
Title is long (89 characters)
Your title is 89 characters, so Google will cut it off around 60: “Top CA Online Classes in Pune and India | Best CA Classes in Pune | Swapnil Patni Classes”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (165 characters)
Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
82 internal links, 37 external
The homepage links to 82 pages on swapnilpatni.com and 37 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.swapnilpatni.com/.
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.swapnilpatni.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://swapnilpatni.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,682 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages share 3 titles
https://swapnilpatni.com/stores/commerce_12th.php and https://swapnilpatni.com/stores/11-12-CBSE.php all use the title “Best 11th & 12th Commerce Classes in Pune & India | SPC Commerce Coac…”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://swapnilpatni.com/ankitapatni_trust.php has no meta description, so Google writes the search snippet from whatever text it finds.
7 pages share a meta description
https://swapnilpatni.com/stores/commerce_12th.php and https://swapnilpatni.com/stores/11-12-CBSE.php use the same meta description. A description written for each page earns more clicks.
8 links to non-canonical URLs
Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://swapnilpatni.com/stores/ca-inter-new-filter.php, whose canonical is https://swapnilpatni.com/stores/pd_gd_course.php. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://swapnilpatni.com/ankitapatni_trust.php has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
2 checks passed
Tap targets are thumb-sized
45 of 46 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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,259 words of copy
The homepage carries about 1,259 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 Us” and “📞 Call Us”.
8 calls to action
The homepage has 8 calls to action, for example “Contact Us”, “📞 Call Us” and “Get in Touch →”.
1 short form
A short form (2 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 7 testimonial or review blocks, a star rating, 1 trust badge and “400K+ Students”.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
4 cookies set on arrival
4Opening the homepage sets 4 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.
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 swapnilpatni.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on swapnilpatni.com, including 14 speed issues, 6 SEO issues 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.