chardan.com website review

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

About 601 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

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

Your mobile performance score is 54 (desktop: 70). Pages that score under 90 lose visitors before the first paint.

6 third-party services load with your homepage (Google Tag Manager, Usercentrics CMP and Mouseflow and others), adding 4.9 MB and 478 ms of main-thread time.

5 files are served with short cache lifetimes, so returning visitors download them again (80 KiB).

105 KiB could be saved by minifying JavaScript.

prismic.io costs a phone 0 ms of main-thread work and 4.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.

Google Tag Manager costs a phone 340 ms of main-thread work and 347 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.

8 images could be 71 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

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

61 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 16.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enhance your experience of our website. B…”.

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

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

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

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

12 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 6.6 MB in 72 requests on a phone: media 4.2 MB (1), scripts 1.2 MB (18) and fonts 599 KiB (4). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 dropdown has no label.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

10 images have no alt text, which hurts accessibility and image search.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

Your title is 72 characters, so Google will cut it off around 60: “Investment Banking for Digital Assets, Technology, and Biotech | Chardan”.

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

Your meta description is 182 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.

There is no robots.txt at chardan.com/robots.txt, the first file search crawlers ask for.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 71 pages on chardan.com and 7 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 /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.

/fintech, /research and /privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

/privacy-policy, /legal-disclosures-policies, /business-continuity-plan and /formcrs have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Content security policy”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 709 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). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 5 cookies (measured from a US location before any click).

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