doclandservices.com website review

About 4.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.2 s faster on a phone.

21 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.5 s.

69 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).

canva.com costs a phone 2.6 s of main-thread work and 5.8 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.

About 310 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

Your mobile performance score is 32 (desktop: 46). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 9.9 s on main-thread work while loading, 5.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (canva.com, YouTube and anyflip.com and others), adding 9.6 MB and 3.7 s of main-thread time.

16 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

243 KiB could be saved by minifying JavaScript.

YouTube costs a phone 636 ms of main-thread work and 1.9 MB 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.

18 long tasks block the main thread while loading, the longest for 535 ms. During a long task the page ignores taps.

Polyfills for old browsers add 43 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

anyflip.com costs a phone 190 ms of main-thread work and 1.3 MB 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.

41 KiB could be saved by minifying CSS.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

The first text or image appears after 8.7 s on a phone. Good is under 1.8 s.

Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Visually, the page fills in at 39.2 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 70.6 s. Good is under 3.8 s.

Scripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.

11 images have no width and height attributes, so the layout jumps as each one loads.

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.

Your homepage downloads 14.0 MB in 327 requests on a phone: scripts 8.1 MB (112), images 4.0 MB (72) and fonts 866 KiB (23). Under 2 MB keeps phones on slow connections fast.

9 images are downloaded at several times the size a phone draws them, for example 651940414080320241313.png at 2,380 px wide, shown at 322 px. Resized copies would save about 1.9 MB.

10 images (2.5 MB) 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.

9 images further down the page (2.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 3.97 g of CO₂e: 476.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 dropdowns have no label.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

75 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

7 frames have no title, so screen-reader users cannot tell what they contain.

2 tap targets are too small or too close together to hit reliably with a finger.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 56 elements on the page fail this check, rated moderate by axe-core.

24 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 visible links have no text or label, so screen readers cannot say where they go.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Headings skip levels (h2 → h5, h2 → h6 and h2 → h5), which makes the page harder to scan with a screen reader.

Your title is 138 characters, so Google will cut it off around 60: “Docland Services : India's Largest Professional Risk Management Service Provider for Doct…”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 8 <h1> headlines (“Vision / Our Commitments”, “Your Membership Calculator” and “Your Premium Calculator”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 265 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://doclandservices.com/sitemap.xml, so Google discovers your pages only by following links.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 33 pages on doclandservices.com and 8 external pages.

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.

There is no https://doclandservices.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.

https://doclandservices.com/Blog.aspx, https://doclandservices.com/Credibility.aspx, https://doclandservices.com/JoinUs.aspx, https://doclandservices.com/DoctorPatientRelation.aspx, https://doclandservices.com/StepsAgainstLitigation.aspx and https://doclandservices.com/OtherLegalAvenues.aspx and 4 others all use the title “Docland Services: India's Largest Professional Risk Management Servic…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://doclandservices.com/Blog.aspx, https://doclandservices.com/Credibility.aspx, https://doclandservices.com/JoinUs.aspx, https://doclandservices.com/DoctorPatientRelation.aspx, https://doclandservices.com/StepsAgainstLitigation.aspx and https://doclandservices.com/OtherLegalAvenues.aspx and 4 others use the same meta description. A description written for each page earns more clicks.

https://doclandservices.com/Credibility.aspx, https://doclandservices.com/JoinUs.aspx, https://doclandservices.com/DoctorPatientRelation.aspx, https://doclandservices.com/StepsAgainstLitigation.aspx, https://doclandservices.com/OtherLegalAvenues.aspx and https://doclandservices.com/Structure.aspx and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://doclandservices.com/JoinUs.aspx, https://doclandservices.com/Structure.aspx and https://doclandservices.com/Grievance.aspx have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

12 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

Your longest form asks for 25 fields (0 required). Every extra field lowers completion.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 854 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics 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.

Opening the homepage sets 7 cookies, 2 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.