Website review, no card needed

elloproducts.com logo

elloproducts.com website review

Visit site (opens in a new tab)Reviewed 8 November 202639 issues · 73 checks

This review found 39 issues worth fixing on elloproducts.com, 15 of them high impact, across 73 checks. The most urgent: page weight: 83.6 MB in 490 requests. 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.4 s2.1 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.2 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
174 ms138 msMay 16Oct 31154 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026145 ms
May 23, 2026145 ms
May 30, 2026145 ms
Jun 6, 2026142 ms
Jun 13, 2026144 ms
Jun 20, 2026145 ms
Jun 27, 2026146 ms
Jul 4, 2026148 ms
Jul 11, 2026146 ms
Jul 18, 2026145 ms
Jul 25, 2026146 ms
Aug 1, 2026148 ms
Aug 8, 2026153 ms
Aug 15, 2026155 ms
Aug 22, 2026157 ms
Aug 29, 2026155 ms
Sep 5, 2026156 ms
Sep 12, 2026154 ms
Sep 19, 2026158 ms
Sep 26, 2026162 ms
Oct 3, 2026165 ms
Oct 10, 2026170 ms
Oct 17, 2026170 ms
Oct 24, 2026162 ms
Oct 31, 2026154 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 elloproducts.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. elloproducts.com at 0.8 s0.8 s
  2. elloproducts.com at 1.7 s1.7 s
  3. elloproducts.com at 2.5 s2.5 s
  4. elloproducts.com at 3.4 s3.4 s
  5. elloproducts.com at 4.2 s4.2 s
  6. elloproducts.com at 5.1 s5.1 s
  7. elloproducts.com at 5.9 s5.9 s
  8. elloproducts.com at 6.7 s6.7 s

Speed

14 to fix38
  • Use efficient cache lifetimes

    4.9 s · 1.0 MB

    27 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

  • Reduce unused JavaScript

    4.2 s · 945 KiB

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

  • Improve image delivery

    3.6 s · 932 KiB

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

  • Mobile performance score: 38

    38/100

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

  • Main-thread work: 9.3 s

    A phone's processor spends 9.3 s on main-thread work while loading, 2.9 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 (Google Tag Manager, monkcommerce.app and rebuyengine.com and others), adding 2.6 MB and 1.6 s of main-thread time.

  • Minify JavaScript

    620 ms · 54 KiB

    54 KiB could be saved by minifying JavaScript.

  • Render-blocking requests

    600 ms

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

  • monkcommerce.app adds 359 ms

    359 ms

    monkcommerce.app costs a phone 359 ms of main-thread work and 647 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 Tag Manager adds 380 ms

    380 ms

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

  • 20 long tasks on the main thread

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

  • rebuyengine.com adds 237 ms

    237 ms

    rebuyengine.com costs a phone 237 ms of main-thread work and 331 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.

  • Attentive adds 161 ms

    161 ms

    Attentive costs a phone 161 ms of main-thread work and 1.0 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.

  • 1,782 HTML elements

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

  • Legacy JavaScript

    150 ms · 59 KiB

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

  • Reduce unused CSS

    70 ms · 31 KiB

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

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 71 ms

    71 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 29.9 s

    29.9 s

    Your largest element takes 29.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ello”.

  • Time to Interactive: 31.5 s

    31.5 s

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

  • Speed Index: 14.0 s

    14.0 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 16 images without width and height

    16 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 145 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +1%

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

5 checks passed
  • Real-user INP: 105 ms

    105 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 463 ms

    463 ms

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

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

2 to fix64
  • Page weight: 83.6 MB in 490 requests

    83.6 MB

    Your homepage downloads 83.6 MB in 490 requests on a phone: media 76.9 MB (16), images 3.0 MB (132) and scripts 2.2 MB (126). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    2026.10.02.26_EL_DTC-Navigation_Website_02.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 23.7 g of CO₂ per visit

    23.69 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 10095
  • 11 links without text

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

  • 10 form fields without a label

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

1 checks passed
  • 18 automated accessibility rules passed

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

SEO

5 to fixGoogle 10076
  • No H1 headline

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

  • No structured data

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

  • Meta description is long (180 characters)

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

4 checks passed
  • Title: 55 characters

    Your title is a healthy 55 characters: “Ello® | Water Bottles, Food Storage, Travel Mugs & More”.

  • Canonical URL set

    The canonical URL is https://www.elloproducts.com/.

  • 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.elloproducts.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 612 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

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.

  • llms.txt published

    The site publishes https://www.elloproducts.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    255 of 286 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

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

  • About 612 words of copy

    The homepage carries about 612 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All” and “Clean Start”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Hotjar.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 1 more (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.

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies, 1 of them by other companies (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.

  • 40 other companies contacted

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

Apps on your store

Your storefront loads 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Yotpo Product Reviews · Bundler Bundles App · Attentive · Klaviyo Email Marketing Sms · Powerful Form Builder · nfcube.com · nice-team.net · cloudfront.net · sealsubscriptions.com · rebuyengine.com · attn.tv

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Hotjar
Hosting
Shopify

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 elloproducts.com, including 22 speed issues, 5 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