Website review, no card needed

continental.coffee logo

continental.coffee website review

Visit site (opens in a new tab)Reviewed 1 November 202637 issues · 75 checks

This review found 37 issues worth fixing on continental.coffee, 15 of them high impact, across 75 checks. The most urgent: font display. 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

Full-page screenshot of continental.coffee (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. continental.coffee at 1.6 s1.6 s
  2. continental.coffee at 3.3 s3.3 s
  3. continental.coffee at 4.9 s4.9 s
  4. continental.coffee at 6.5 s6.5 s
  5. continental.coffee at 8.2 s8.2 s
  6. continental.coffee at 9.8 s9.8 s
  7. continental.coffee at 11.5 s11.5 s
  8. continental.coffee at 13.1 s13.1 s

Speed

6 to fix43
  • Font display

    3.0 s

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

  • Render-blocking requests

    1.6 s

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

  • Reduce unused JavaScript

    1.4 s · 158 KiB

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

  • Mobile performance score: 43

    43/100

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

  • Improve image delivery

    600 ms · 407 KiB

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

  • Reduce unused CSS

    300 ms · 45 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and Cloudflare and others), adding 477 KiB and 240 ms of main-thread time.

  • Use efficient cache lifetimes

    158 KiB

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

  • Minify CSS

    150 ms · 4 KiB

    4 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 122 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    10 KiB

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 504 ms

    504 ms

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

Core Web Vitals

6 to fix40
  • Speed Index: 15.2 s

    15.2 s

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

  • Cumulative Layout Shift: 0.602

    0.602

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

  • Largest Contentful Paint: 6.2 s

    6.2 s

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

  • Time to Interactive: 6.2 s

    6.2 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 9 images without width and height

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

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Total Blocking Time: 95 ms

    95 ms

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

Images and page weight

1 to fix90
  • 7 images in older formats

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

  • 3 images below the first screen load straight away

    3 images further down the page (212 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.56 g

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

2 checks passed
  • Page weight: 2.0 MB in 175 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 175 requests on a phone: images 1.2 MB (140), scripts 406 KiB (16) and fonts 247 KiB (3). That is a lean page.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8289
  • 5 tap targets too small

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

  • 162 images without alt text

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

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

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

  • 6 links without text

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

1 checks passed
  • 30 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 6 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 5441
  • Page is set to noindex

    The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • No structured data

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

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

  • No XML sitemap

    No XML sitemap at https://www.continental.coffee/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 29 internal links, 8 external

    The homepage links to 29 pages on continental.coffee and 8 external pages.

3 checks passed
  • Title: 51 characters

    Your title is a healthy 51 characters: “Continental Coffee – India's Favourite Coffee Brand”.

  • Canonical URL set

    The canonical URL is https://www.continental.coffee/.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

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

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

Other pages

3 to fix83
  • 10 linked pages hidden from search

    https://www.continental.coffee/instant, https://www.continental.coffee/malgudi, https://www.continental.coffee/coffee-mix, https://www.continental.coffee/campaigns, https://www.continental.coffee/blog and https://www.continental.coffee/contact and 4 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 10 pages without a meta description

    https://www.continental.coffee/instant, https://www.continental.coffee/malgudi, https://www.continental.coffee/coffee-mix, https://www.continental.coffee/campaigns, https://www.continental.coffee/blog and https://www.continental.coffee/contact and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://www.continental.coffee/instant, https://www.continental.coffee/malgudi, https://www.continental.coffee/coffee-mix, https://www.continental.coffee/campaigns, https://www.continental.coffee/blog and https://www.continental.coffee/speciality and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 internal pages checked

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

4 checks passed
  • Linked pages load

    All 10 pages we checked loaded without an error.

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

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9271
  • 2 broken images

    2 images failed to load on a phone, for example https://www.continental.coffee/.

  • 11 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 57 words

    The homepage has only about 57 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

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

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

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop” and “contact us”.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

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

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.

  • 2 cookies set on arrival

    2

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

  • 7 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on continental.coffee, including 12 speed issues, 7 SEO issues and 3 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