Website review, no card needed

8thandroast.com logo

8thandroast.com website review

Visit site (opens in a new tab)Reviewed 27 October 202641 issues · 88 checks

This review found 41 issues worth fixing on 8thandroast.com, 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
1.8 s1.4 sJun 13Oct 241.7 s
Show as table
DateReal-visitor load time (LCP)
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.6 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.5 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
92 ms85 msJun 20Oct 2487 ms
Show as table
DateReal-visitor tap response (INP)
Jun 20, 202687 ms
Jun 27, 202686 ms
Jul 4, 202686 ms
Jul 11, 202687 ms
Jul 18, 202688 ms
Jul 25, 202688 ms
Aug 1, 202688 ms
Aug 8, 202691 ms
Aug 15, 202687 ms
Aug 22, 202687 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202688 ms
Sep 26, 202688 ms
Oct 3, 202690 ms
Oct 10, 202690 ms
Oct 17, 202688 ms
Oct 24, 202687 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 8thandroast.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 8thandroast.com at 0.4 s0.4 s
  2. 8thandroast.com at 0.8 s0.8 s
  3. 8thandroast.com at 1.2 s1.2 s
  4. 8thandroast.com at 1.6 s1.6 s
  5. 8thandroast.com at 1.9 s1.9 s
  6. 8thandroast.com at 2.3 s2.3 s
  7. 8thandroast.com at 2.7 s2.7 s
  8. 8thandroast.com at 3.1 s3.1 s

Speed

13 to fix48
  • Improve image delivery

    5.5 s · 4.8 MB

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

  • Reduce unused JavaScript

    2.7 s · 490 KiB

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

  • Use efficient cache lifetimes

    1.1 s · 230 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 48

    48/100

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

  • Main-thread work: 4.7 s

    A phone's processor spends 4.7 s on main-thread work while loading, 1.6 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 (JSDelivr CDN, Accessibe Accessibility Overlay and Bigcommerce and others), adding 10.4 MB and 1.3 s of main-thread time.

  • Bigcommerce adds 196 ms

    196 ms

    Bigcommerce costs a phone 196 ms of main-thread work and 9.2 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.

  • Reduce unused CSS

    450 ms · 70 KiB

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

  • JSDelivr CDN adds 346 ms

    346 ms

    JSDelivr CDN costs a phone 346 ms of main-thread work and 16 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.

  • Accessibe Accessibility Overlay adds 268 ms

    268 ms

    Accessibe Accessibility Overlay costs a phone 268 ms of main-thread work and 243 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.

  • 1,694 HTML elements

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

  • smile.io adds 100 ms

    100 ms

    smile.io costs a phone 100 ms of main-thread work and 436 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.

  • Legacy JavaScript

    150 ms · 41 KiB

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

  • 9 long tasks on the main thread

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

  • Minify JavaScript

    120 ms · 12 KiB

    12 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 23 ms

    23 ms

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

Core Web Vitals

6 to fix100
  • 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 text “exploring the world of”.

  • Time to Interactive: 26.8 s

    26.8 s

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

  • First Contentful Paint: 6.8 s

    6.8 s

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

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

  • Total Blocking Time: 337 ms

    337 ms

    Scripts block taps and scrolling for 337 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

    +1%

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

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

    +13%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 88 ms

    88 ms

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

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

    1.6 s

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

  • Real-user TTFB: 751 ms

    751 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix28
  • Page weight: 10.5 MB in 108 requests

    10.5 MB

    Your homepage downloads 10.5 MB in 108 requests on a phone: images 5.4 MB (20), media 3.5 MB (1) and scripts 1.1 MB (57). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

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

  • 5 images far larger than shown

    2.0 MB

    5 images are downloaded at several times the size a phone draws them, for example h34a7345-1.jpeg at 2,048 px wide, shown at 349 px. Resized copies would save about 2.0 MB.

  • 6 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (210 KiB) is 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 3.0 g of CO₂ per visit

    2.99 g

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

Accessibility

5 to fixGoogle 9794
  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 15 links without text

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

4 to fixGoogle 9276
  • No meta description

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

  • Title is short (13 characters)

    Your title is only 13 characters: “8th and Roast”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 2 problems

    Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: sameAs is an empty list”.

  • 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 X (Twitter) card tag

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

  • 180 internal links, 15 external

    The homepage links to 180 pages on 8thandroast.com and 15 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “exploring the world of exceptional coffee together”.

  • Canonical URL set

    The canonical URL is https://8thandroast.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://8thandroast.com/sitemap.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 (1,138 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix81
  • 2 pages share a title

    https://8thandroast.com/shop/explore/all-coffees and https://8thandroast.com/collections/all-coffees all use the title “All Coffee - 8&R Coffee Co.”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://8thandroast.com/pages/about, https://8thandroast.com/collections/chocolate, https://8thandroast.com/collections/citrus, https://8thandroast.com/collections/fruity, https://8thandroast.com/collections/spicy and https://8thandroast.com/collections/sweet and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://8thandroast.com/shop/explore/all-coffees and https://8thandroast.com/collections/all-coffees use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://8thandroast.com/shop/explore/all-coffees, whose canonical is https://8thandroast.com/collections/all-coffees. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    46 of 54 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 856 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW” and “Shop”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “SHOP NOW”, “Shop Shop” and “Shop Now”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 15 cookies set on arrival

    15

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

  • 21 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
BigCommerce
Analytics
Google Analytics
Hosting
BigCommerce

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on 8thandroast.com, including 19 speed issues, 4 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