Website review, no card needed

thelocavore.in logo

thelocavore.in website review

Visit site (opens in a new tab)Reviewed 6 November 202645 issues · 88 checks

This review found 45 issues worth fixing on thelocavore.in, 16 of them high impact, across 88 checks. The most urgent: improve image delivery. 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
2.9 s2.5 sMay 16Oct 312.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.7 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Oct 31, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
114 ms91 msMay 16Oct 31105 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202697 ms
May 23, 202695 ms
May 30, 202694 ms
Jun 6, 202694 ms
Jun 13, 202696 ms
Jun 20, 2026101 ms
Jun 27, 2026100 ms
Jul 4, 2026105 ms
Jul 11, 2026107 ms
Jul 18, 2026103 ms
Jul 25, 2026107 ms
Aug 1, 2026101 ms
Aug 8, 202699 ms
Aug 15, 2026102 ms
Aug 22, 2026103 ms
Aug 29, 2026108 ms
Sep 5, 2026104 ms
Sep 12, 2026103 ms
Sep 19, 2026111 ms
Sep 26, 2026107 ms
Oct 3, 2026108 ms
Oct 10, 2026110 ms
Oct 17, 2026104 ms
Oct 24, 2026104 ms
Oct 31, 2026105 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 thelocavore.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thelocavore.in at 0.6 s0.6 s
  2. thelocavore.in at 1.2 s1.2 s
  3. thelocavore.in at 1.8 s1.8 s
  4. thelocavore.in at 2.4 s2.4 s
  5. thelocavore.in at 3.0 s3.0 s
  6. thelocavore.in at 3.6 s3.6 s
  7. thelocavore.in at 4.1 s4.1 s
  8. thelocavore.in at 4.7 s4.7 s

Speed

15 to fix48
  • Improve image delivery

    4.0 s · 5.3 MB

    56 images could be 5.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.

  • Render-blocking requests

    8.0 s

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

  • Reduce unused CSS

    1.2 s · 235 KiB

    About 235 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.

  • Mobile performance score: 48

    48/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Cloudflare CDN and others), adding 8.1 MB and 859 ms of main-thread time.

  • Reduce unused JavaScript

    610 ms · 472 KiB

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

  • WordPress adds 0 ms

    0 ms

    WordPress costs a phone 0 ms of main-thread work and 7.1 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.

  • Use efficient cache lifetimes

    300 ms · 278 KiB

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

  • Reduce initial server response time

    511 ms

    Reduce initial server response time. Google estimates savings of 511 ms on a phone.

  • Document request latency

    500 ms

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

  • Google Tag Manager adds 413 ms

    413 ms

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

  • Facebook adds 258 ms

    258 ms

    Facebook costs a phone 258 ms of main-thread work and 301 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.

  • Main-thread work: 2.6 s

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

  • 1,514 HTML elements

    The page has 1,514 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Server response: 611 ms

    611 ms

    Your server takes 611 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Minify CSS

    150 ms · 14 KiB

    14 KiB could be saved by minifying CSS.

  • 11 long tasks on the main thread

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

  • Legacy JavaScript

    13 KiB

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

  • Forced reflow

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 11.1 s

    11.1 s

    Your largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Eating Against the Tide: Stories, Recipes, and Research fro…”.

  • Speed Index: 10.3 s

    10.3 s

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

  • Time to Interactive: 13.1 s

    13.1 s

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

  • First Contentful Paint: 4.6 s

    4.6 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Total Blocking Time: 394 ms

    394 ms

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

4 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.016

    0.016

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

Images and page weight

4 to fix28
  • Page weight: 9.2 MB in 220 requests

    9.2 MB

    Your homepage downloads 9.2 MB in 220 requests on a phone: images 7.5 MB (71), scripts 1.2 MB (59) and stylesheets 356 KiB (78). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.

  • 27 images far larger than shown

    1.4 MB

    27 images are downloaded at several times the size a phone draws them, for example So-Himalayas8.png at 800 px wide, shown at 222 px. Resized copies would save about 1.4 MB.

  • 35 images below the first screen load straight away

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

  • 4 images in older formats

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

  • About 2.6 g of CO₂ per visit

    2.60 g

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

Accessibility

5 to fixGoogle 9493
  • 18 text elements with low contrast

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

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

    Main 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 main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 78 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

3 to fixGoogle 8585
  • No meta description

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

  • No social preview image

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

  • 12 links with vague text

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

  • 295 internal links, 12 external

    The homepage links to 295 pages on thelocavore.in and 12 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Eating Against the Tide: Stories, Recipes, and Research from Mumbai’s Coastline”.

  • Title: 38 characters

    Your title is a healthy 38 characters: “The Locavore - Doing Good Through Food”.

  • Canonical URL set

    The canonical URL is https://thelocavore.in/.

  • Structured data in place

    Structured data found: Article, Organization, Person, 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://thelocavore.in/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

    The site publishes https://thelocavore.in/llms.txt (72 KiB, 200 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 9 pages without a meta description

    https://thelocavore.in/stories, https://thelocavore.in/category/stories/features/books-on-food, https://thelocavore.in/category/stories/features/culture, https://thelocavore.in/category/stories/features/personal-essay, https://thelocavore.in/category/stories/features/from-the-fields and https://thelocavore.in/category/stories/features/locavore-champions and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://thelocavore.in/everyday-locavores has 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 152 found) and read each the way a search engine does.

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

  • 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

4 to fixGoogle 9270
  • 1 broken image

    1 image failed to load on a phone, for example https://i0.wp.com/thelocavore.in/wp-content/uploads/2026/08/Urtica.png?fit=800%2C600&ssl=1.

  • 30 small tap targets

    30 of 50 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 “Failed to load resource: the server responded with a status of 400 ()”.

  • 3 distorted images

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

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.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 1,493 words of copy

    The homepage carries about 1,493 words of visible text.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Sign up” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 9 customer or partner logos and 64 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 5 cookies set on arrival

    5

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 thelocavore.in, 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
Hostinger

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on thelocavore.in, including 23 speed issues, 3 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