Website review, no card needed

maineroast.com logo

maineroast.com website review

Visit site (opens in a new tab)Reviewed 6 November 202633 issues · 70 checks

This review found 33 issues worth fixing on maineroast.com, 10 of them high impact, across 70 checks. The most urgent: avoid multiple page redirects. 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 maineroast.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. maineroast.com at 0.5 s0.5 s
  2. maineroast.com at 1.1 s1.1 s
  3. maineroast.com at 1.6 s1.6 s
  4. maineroast.com at 2.2 s2.2 s
  5. maineroast.com at 2.7 s2.7 s
  6. maineroast.com at 3.2 s3.2 s
  7. maineroast.com at 3.8 s3.8 s
  8. maineroast.com at 4.3 s4.3 s

Speed

4 to fix68
  • Avoid multiple page redirects

    2.0 s

    The page goes through 1 redirect before it starts loading, costing about 2.0 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    1.0 s · 240 KiB

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

  • Mobile performance score: 68

    68/100

    Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    300 ms

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

  • Use efficient cache lifetimes

    150 ms · 197 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Snapchat, Attentive and Afterpay and others), adding 362 KiB and 188 ms of main-thread time.

  • Font display

    100 ms

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 54 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    26 KiB

    About 26 KiB of CSS is downloaded but never applied on this page.

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

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

5 to fix80
  • Speed Index: 9.0 s

    9.0 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “*These statements have not been evaluated by the Food and D…”. Most of its time is element render delay (4.3 s).

  • Time to Interactive: 6.8 s

    6.8 s

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

  • 1 image without width and height

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

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 4 ms

    4 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 237 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 237 requests on a phone: other files 992 KiB (155), scripts 842 KiB (61) and images 137 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.59 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 8294
  • 2 images without alt text

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 32 automated accessibility rules passed

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

SEO

6 to fixGoogle 6965
  • Error status code

    The page answers with an error status, so search engines may drop it.

  • Title is long (85 characters)

    Your title is 85 characters, so Google will cut it off around 60: “Maine Roast™ Protein Coffee: Give your mornings a boost! – Maine Roast Protein Coffee”.

  • Meta description is long (240 characters)

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

  • Structured data has 2 problems

    Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: sameAs is not an absolute URL ("www.facebook.com/mrproteincoffee")”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • One H1 headline

    Your <h1> is empty.

  • 11 internal links, 5 external

    The homepage links to 11 pages on maineroast.com and 5 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://maineroast.com/.

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

AI search readiness

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

    Your Organization JSON-LD is missing logo, 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.

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://maineroast.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

6 to fix50
  • 1 page without a title

    https://maineroast.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 page points its canonical at the homepage

    https://maineroast.com/products/maine-roast-protein-coffee declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 1 linked page hidden from search

    https://maineroast.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    / and https://maineroast.com/products/maine-roast-protein-coffee all use the title “Maine Roast™ Protein Coffee: Give your mornings a boost! – Maine Roas…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://maineroast.com/customer_authentication/redirect, https://maineroast.com/blogs/recipes, https://maineroast.com/blogs/news, https://maineroast.com/pages/contact and https://maineroast.com/pages/resellers-pricing have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://maineroast.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://maineroast.com/products/maine-roast-protein-coffee and https://maineroast.com/pages/contact 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.

  • 8 internal pages checked

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

1 checks passed
  • Linked pages load

    All 8 pages we checked loaded without an error.

Best practices

3 to fixGoogle 7385
  • 13 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 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 ()”.

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

  • Only about 75 words

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

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “Resellers Pricing”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Start your order”, “Sign Up” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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, Klaviyo and Meta Pixel 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.

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 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 maineroast.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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

snapchat.com

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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on maineroast.com, including 9 speed issues, 6 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