Website review, no card needed

condorinblu.com logo

condorinblu.com website review

Visit site (opens in a new tab)Reviewed 21 November 202647 issues · 87 checks

This review found 47 issues worth fixing on condorinblu.com, 16 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
8.9 s4.1 sMay 30Nov 147.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.7 s
Jun 6, 20264.9 s
Jun 13, 20265.0 s
Jun 20, 20264.8 s
Jun 27, 20264.9 s
Jul 4, 20264.8 s
Jul 11, 20264.9 s
Jul 18, 20264.9 s
Jul 25, 20264.9 s
Aug 29, 20267.5 s
Sep 5, 20267.7 s
Sep 12, 20267.5 s
Sep 19, 20267.4 s
Sep 26, 20267.4 s
Oct 3, 20267.4 s
Oct 10, 20267.6 s
Oct 24, 20268.4 s
Oct 31, 20267.6 s
Nov 7, 20267.4 s
Nov 14, 20267.3 s
Real-visitor tap response (INP)75th percentile, phones
134 ms88 msMay 30Oct 1093 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026113 ms
Jun 6, 2026113 ms
Jul 18, 2026129 ms
Oct 10, 202693 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 condorinblu.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. condorinblu.com at 2.3 s2.3 s
  2. condorinblu.com at 4.6 s4.6 s
  3. condorinblu.com at 6.9 s6.9 s
  4. condorinblu.com at 9.2 s9.2 s
  5. condorinblu.com at 11.6 s11.6 s
  6. condorinblu.com at 13.9 s13.9 s
  7. condorinblu.com at 16.2 s16.2 s
  8. condorinblu.com at 18.5 s18.5 s

Speed

10 to fix44
  • Reduce unused JavaScript

    9.2 s · 1.8 MB

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

  • Render-blocking requests

    6.6 s

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

  • Improve image delivery

    4.3 s · 931 KiB

    5 images could be 931 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.3 s faster on a phone.

  • Mobile performance score: 44

    44/100

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

  • Reduce unused CSS

    600 ms · 122 KiB

    About 122 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Font display

    550 ms

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

  • 6 long tasks on the main thread

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

  • Main-thread work: 2.4 s

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

  • Google Tag Manager adds 186 ms

    186 ms

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

  • Google CDN adds 119 ms

    119 ms

    Google CDN costs a phone 119 ms of main-thread work and 352 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google CDN and Google Fonts and others), adding 708 KiB and 306 ms of main-thread time.

  • Minify JavaScript

    150 ms · 13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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.

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

11 to fix50
  • 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: 8.5 s

    8.5 s

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

  • Real-user FCP: 6.4 s

    6.4 s

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

  • Real-user TTFB: 4.8 s

    4.8 s

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

  • Largest Contentful Paint: 26.2 s

    26.2 s

    Your largest element takes 26.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Women”. Most of its time is resource load delay (13.2 s).

  • Speed Index: 24.0 s

    24.0 s

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

  • Time to Interactive: 26.3 s

    26.3 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

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

    +53%

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

  • Total Blocking Time: 562 ms

    562 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

2 checks passed
  • Real-user CLS: 0.05

    0.05

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

  • Cumulative Layout Shift: 0.056

    0.056

    The layout barely moves while loading (CLS 0.056, good is under 0.1).

Images and page weight

4 to fix35
  • Page weight: 4.7 MB in 108 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 108 requests on a phone: scripts 2.4 MB (54), images 1.6 MB (11) and fonts 510 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Aerokids-banner.jpg weighs 678 KiB. On a phone connection a single image that size takes seconds.

  • 7 images in older formats

    7 images (1.4 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.

  • 5 images far larger than shown

    219 KiB

    5 images are downloaded at several times the size a phone draws them, for example Aerokids-banner.jpg at 1,280 px wide, shown at 390 px. Resized copies would save about 219 KiB.

  • About 1.3 g of CO₂ per visit

    1.33 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.33 g of CO₂e: 159.4 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

9 to fixGoogle 8489
  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails 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.

  • Zoom is disabled

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

  • 6 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 25 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8584
  • 6 H1 headlines

    There are 6 <h1> headlines (“Check out our Collection”, “The Condor Footwear Group” and “The Condor Footwear Group”). One clear main headline is easier for people and search engines.

  • Meta description is long (305 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 5 links with vague text

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

  • 1 link crawlers can't follow

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

  • 56 internal links, 19 external

    The homepage links to 56 pages on condorinblu.com and 19 external pages.

5 checks passed
  • Title: 63 characters

    Your title is a healthy 63 characters: “Home - Condor Footwear Group I India's leading Footwear Company”.

  • Canonical URL set

    The canonical URL is https://www.condorgroup.in/.

  • Structured data in place

    Structured data found: BreadcrumbList, ProfilePage, WebPage and WebSite.

  • 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.condorgroup.in/sitemap_index.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://www.condorgroup.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

    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 (790 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 8 pages without a meta description

    https://www.condorgroup.in/about-us/our-mission-values, https://www.condorgroup.in/about-us/credentials, https://www.condorgroup.in/partner-us/exports, https://www.condorgroup.in/partner-us/distribution, https://www.condorgroup.in/news and https://www.condorgroup.in/connect and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.condorgroup.in/news has no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 pages slow to respond

    https://www.condorgroup.in/about-us, https://www.condorgroup.in/about-us/condor-worldwide, https://www.condorgroup.in/about-us/our-mission-values, https://www.condorgroup.in/about-us/manufacturing, https://www.condorgroup.in/about-us/credentials and https://www.condorgroup.in/partner-us and 5 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 7 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “grecaptcha is not defined”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • Thin social proof

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

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

    The homepage carries about 589 words of visible text.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “SHOP”.

  • 3 short forms

    3 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 12 cookies set on arrival

    12

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 condorinblu.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Tucows.com Co.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on condorinblu.com, including 21 speed issues, 5 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

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