Website review, no card needed

mellcon.com logo

mellcon.com website review

Visit site (opens in a new tab)Reviewed 18 October 202642 issues · 90 checks

This review found 42 issues worth fixing on mellcon.com, 14 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.7 s3.4 sApr 25Oct 104.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.8 s
May 2, 20263.9 s
May 9, 20263.7 s
May 16, 20263.6 s
May 23, 20263.6 s
May 30, 20263.5 s
Jun 6, 20263.6 s
Jun 13, 20263.8 s
Jun 20, 20263.7 s
Jun 27, 20263.8 s
Jul 4, 20263.6 s
Jul 11, 20263.6 s
Jul 18, 20263.9 s
Jul 25, 20264.0 s
Aug 1, 20264.2 s
Aug 8, 20264.0 s
Aug 15, 20264.0 s
Aug 22, 20264.1 s
Aug 29, 20264.1 s
Sep 5, 20264.1 s
Sep 12, 20264.1 s
Sep 19, 20264.0 s
Sep 26, 20264.1 s
Oct 3, 20264.5 s
Oct 10, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
193 ms81 msApr 25Oct 10108 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026105 ms
May 9, 202699 ms
May 16, 202694 ms
May 23, 202698 ms
May 30, 202698 ms
Jun 6, 202699 ms
Jun 13, 2026103 ms
Jun 27, 2026101 ms
Jul 4, 2026111 ms
Jul 11, 2026110 ms
Jul 18, 2026112 ms
Jul 25, 2026109 ms
Aug 1, 2026106 ms
Aug 8, 2026105 ms
Aug 15, 2026113 ms
Aug 22, 2026115 ms
Aug 29, 2026105 ms
Sep 5, 2026165 ms
Sep 12, 2026178 ms
Sep 19, 2026171 ms
Sep 26, 2026180 ms
Oct 3, 202697 ms
Oct 10, 2026108 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

Full-page screenshot of mellcon.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mellcon.com at 0.4 s0.4 s
  2. mellcon.com at 0.8 s0.8 s
  3. mellcon.com at 1.2 s1.2 s
  4. mellcon.com at 1.6 s1.6 s
  5. mellcon.com at 2.0 s2.0 s
  6. mellcon.com at 2.4 s2.4 s
  7. mellcon.com at 2.8 s2.8 s
  8. mellcon.com at 3.2 s3.2 s

Speed

4 to fix63
  • Use efficient cache lifetimes

    1.1 s · 502 KiB

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

  • Mobile performance score: 63

    63/100

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

  • Render-blocking requests

    650 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

  • Improve image delivery

    390 KiB

    3 images could be 390 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    150 ms · 148 KiB

    About 148 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Cloudflare CDN and others), adding 286 KiB and 205 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    16 KiB

    About 16 KiB of CSS is downloaded but never applied on this page.

  • Phones get a much slower page than desktops

    Desktop scores 98 but mobile only 63. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 265 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • 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: 4.1 s

    4.1 s

    Real visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 4.3 s

    4.3 s

    Real visitors see the first content after 4.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 2.0 s

    2.0 s

    Real visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Celebrating Over”. Most of its time is element render delay (2.4 s).

  • Speed Index: 5.7 s

    5.7 s

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

  • Time to Interactive: 6.4 s

    6.4 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Cumulative Layout Shift: 0.181

    0.181

    The layout shifts by 0.181 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 105 ms to 108 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 14% slower for real visitors

    +14%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 3.8 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user INP: 102 ms

    102 ms

    Real visitors wait 102 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.03

    0.03

    For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.

  • Total Blocking Time: 63 ms

    63 ms

    Scripts block the page for only 63 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix73
  • 4 images in older formats

    4 images (729 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.

  • 1 image far larger than shown

    233 KiB

    1 image is downloaded at several times the size a phone draws it, for example cphi1.jpg at 1,605 px wide, shown at 348 px. Resized copies would save about 233 KiB.

  • 1 image below the first screen load straight away

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

  • About 0.4 g of CO₂ per visit

    0.41 g

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

1 checks passed
  • Page weight: 1.5 MB in 77 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 77 requests on a phone: images 1,004 KiB (48), scripts 329 KiB (16) and fonts 93 KiB (2). That is a lean page.

Accessibility

12 to fixGoogle 5678
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 3 text elements with low contrast

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

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • <html> element must have a lang attribute (1 element)

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

  • All page content should be contained by landmarks (23 elements)

    All page content should be contained by landmarks: 23 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.

  • 5 form fields without a label

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

  • 3 links without text

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

  • No page language

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

  • 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 71 images in the HTML carry an alt attribute.

  • 27 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 27 passed and 11 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 8381
  • No structured data

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

  • No canonical URL

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

  • Meta description is long (202 characters)

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

  • 1 link crawlers can't follow

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 90 internal links, 3 external

    The homepage links to 90 pages on mellcon.com and 3 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “mellcon Engineers”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Air dryers | Air dryer Manufacturers Suppliers in India - Mellcon”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://mellcon.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://mellcon.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 (826 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 13 pages without an H1

    https://mellcon.com/iso-cetificate.aspx, https://mellcon.com/about_us.aspx, https://mellcon.com/vision-mission.aspx, https://mellcon.com/promoter.aspx, https://mellcon.com/core.aspx and https://mellcon.com/infrastructure.aspx and 7 others have 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 52 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

3 to fixGoogle 9676
  • 1 broken image

    1 image failed to load on a phone, for example https://mellcon.com/.

  • 19 small tap targets

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

  • 3 distorted images

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

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

1 to fix83
  • 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.

  • 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 563 words of copy

    The homepage carries about 563 words of visible text.

5 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks, 56 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 10 other companies contacted

    Loading the homepage contacts 10 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 mellcon.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
Analytics
Google Analytics

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on mellcon.com, including 14 speed issues, 6 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25