Website review, no card needed

eleve.co logo

eleve.co website review

Visit site (opens in a new tab)Reviewed 1 November 202639 issues · 82 checks

This review found 39 issues worth fixing on eleve.co, 20 of them high impact, across 82 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
5.3 s3.8 sMay 9Oct 245.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.2 s
May 16, 20264.7 s
May 23, 20264.8 s
May 30, 20264.7 s
Jun 6, 20265.0 s
Jun 13, 20265.1 s
Jun 20, 20264.7 s
Jun 27, 20264.9 s
Jul 4, 20264.5 s
Jul 11, 20264.6 s
Jul 18, 20265.1 s
Jul 25, 20265.1 s
Aug 1, 20265.1 s
Aug 8, 20265.0 s
Aug 15, 20265.0 s
Aug 22, 20264.7 s
Aug 29, 20264.5 s
Sep 5, 20264.3 s
Sep 12, 20264.0 s
Sep 19, 20264.1 s
Sep 26, 20264.5 s
Oct 3, 20265.0 s
Oct 10, 20265.0 s
Oct 17, 20265.0 s
Oct 24, 20265.0 s
Real-visitor tap response (INP)75th percentile, phones
163 ms113 msMay 9Aug 15119 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026143 ms
May 16, 2026143 ms
May 23, 2026143 ms
May 30, 2026150 ms
Jun 6, 2026150 ms
Jun 13, 2026157 ms
Jun 20, 2026134 ms
Jun 27, 2026135 ms
Jul 4, 2026128 ms
Jul 11, 2026146 ms
Jul 18, 2026157 ms
Jul 25, 2026134 ms
Aug 1, 2026136 ms
Aug 8, 2026133 ms
Aug 15, 2026119 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 eleve.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eleve.co at 0.7 s0.7 s
  2. eleve.co at 1.5 s1.5 s
  3. eleve.co at 2.2 s2.2 s
  4. eleve.co at 2.9 s2.9 s
  5. eleve.co at 3.7 s3.7 s
  6. eleve.co at 4.4 s4.4 s
  7. eleve.co at 5.1 s5.1 s
  8. eleve.co at 5.9 s5.9 s

Speed

13 to fix35
  • Improve image delivery

    15.6 s · 18.3 MB

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

  • Reduce unused JavaScript

    4.6 s · 840 KiB

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

  • Use efficient cache lifetimes

    2.3 s · 340 KiB

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

  • Reduce unused CSS

    1.5 s · 203 KiB

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 4.2 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Squarespace, Google Tag Manager and Facebook and others), adding 2.6 MB and 2.0 s of main-thread time.

  • Squarespace adds 992 ms

    992 ms

    Squarespace costs a phone 992 ms of main-thread work and 1.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.

  • Render-blocking requests

    850 ms

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

  • Legacy JavaScript

    450 ms · 115 KiB

    Polyfills for old browsers add 115 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

  • Google Tag Manager adds 400 ms

    400 ms

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

  • 18 long tasks on the main thread

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

  • Facebook adds 252 ms

    252 ms

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

  • Font display

    100 ms

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

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

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 41 ms

    41 ms

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

Core Web Vitals

10 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: 5.0 s

    5.0 s

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

  • Real-user FCP: 4.8 s

    4.8 s

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

  • Largest Contentful Paint: 44.4 s

    44.4 s

    Your largest element takes 44.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AI-Platform Powered Influencer Marketing!”.

  • Time to Interactive: 45.2 s

    45.2 s

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

  • Speed Index: 11.7 s

    11.7 s

    Visually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 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.

  • Total Blocking Time: 979 ms

    979 ms

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • 1 image without width and height

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

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

    +12%

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

3 checks passed
  • Real-user CLS: 0.01

    0.01

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

  • Tap response (INP) got 12% faster for real visitors

    -12%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix38
  • 3 images over 500 KB

    3 images weigh 21.7 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 20.3 MB in 101 requests

    20.3 MB

    Your homepage downloads 20.3 MB in 101 requests on a phone: images 17.6 MB (10), scripts 2.2 MB (63) and fonts 225 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (21.7 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.

  • 1 image below the first screen load straight away

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

  • About 5.8 g of CO₂ per visit

    5.76 g

    By the Sustainable Web Design model, a visit to your homepage emits about 5.76 g of CO₂e: 691.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 are sized for phones

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

Accessibility

1 to fixGoogle 9598
  • Links must have discernible text (6 elements)

    Links must have discernible text: 6 elements on the page fail this check, rated serious by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

2 to fixGoogle 10091
  • Meta description is long (236 characters)

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

  • Structured data has 2 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/62a99fb8e114e544e07…”.

  • 38 internal links, 9 external

    The homepage links to 38 pages on eleve.co and 9 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “AI-Platform Powered Influencer Marketing!”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “Best Influencer Marketing Agency in India | Eleve”.

  • Canonical URL set

    The canonical URL is https://www.eleve.co/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.eleve.co/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.eleve.co/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 (759 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix58
  • 1 linked page is broken

    Your homepage links to https://www.eleve.co/contact, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 linked page hidden from search

    https://www.eleve.co/contact-us1 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 7 pages without a meta description

    https://www.eleve.co/contact-us1, https://www.eleve.co/nivea-milk-delights, https://www.eleve.co/makemytrip-myindia, https://www.eleve.co/samsung-galaxynote20ultra-campaign, https://www.eleve.co/star-breaktheloop-influencercampaign and https://www.eleve.co/cultfit-x-hrx-program-campaign and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.eleve.co/services, https://www.eleve.co/influencermarketingblog, https://www.eleve.co/contact-us1, https://www.eleve.co/nivea-milk-delights and https://www.eleve.co/makemytrip-welcome-to-arabia have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.eleve.co/influencermarketingblog, https://www.eleve.co/makemytrip-myindia and https://www.eleve.co/makemytrip-welcome-to-arabia have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 13 internal pages checked

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

3 checks passed
  • 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 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/62a99fb8e114e544e0780567/48/5c5a…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix71
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

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

  • No map or directions link

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

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

    The homepage carries about 571 words of visible text.

5 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “CONTACT US”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 9 cookies set on arrival

    9

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

  • 16 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Squarespace
Analytics
Google Analytics | Google Tag Manager
Hosting
Squarespace

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on eleve.co, including 23 speed issues, 2 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