Website review, no card needed

nmpinoncoffee.com logo

nmpinoncoffee.com website review

Visit site (opens in a new tab)Reviewed 7 November 202631 issues · 80 checks

This review found 31 issues worth fixing on nmpinoncoffee.com, 8 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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.3 s863 msMay 16Oct 31940 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.1 s
Jul 11, 20261.2 s
Jul 18, 20261.0 s
Jul 25, 20261.0 s
Aug 1, 20261.1 s
Aug 8, 20261.0 s
Aug 15, 20261.0 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.0 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.0 s
Oct 3, 2026949 ms
Oct 10, 2026914 ms
Oct 17, 2026913 ms
Oct 24, 2026918 ms
Oct 31, 2026940 ms
Real-visitor tap response (INP)75th percentile, phones
94 ms83 msMay 16Oct 3185 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202692 ms
May 23, 202693 ms
May 30, 202692 ms
Jun 6, 202691 ms
Jun 13, 202689 ms
Jun 20, 202690 ms
Jun 27, 202691 ms
Jul 4, 202691 ms
Jul 11, 202691 ms
Jul 18, 202688 ms
Jul 25, 202688 ms
Aug 1, 202687 ms
Aug 8, 202688 ms
Aug 15, 202688 ms
Aug 22, 202688 ms
Aug 29, 202688 ms
Sep 5, 202688 ms
Sep 12, 202688 ms
Sep 19, 202688 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202685 ms
Oct 17, 202684 ms
Oct 24, 202685 ms
Oct 31, 202685 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 nmpinoncoffee.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nmpinoncoffee.com at 0.4 s0.4 s
  2. nmpinoncoffee.com at 0.8 s0.8 s
  3. nmpinoncoffee.com at 1.1 s1.1 s
  4. nmpinoncoffee.com at 1.5 s1.5 s
  5. nmpinoncoffee.com at 1.9 s1.9 s
  6. nmpinoncoffee.com at 2.3 s2.3 s
  7. nmpinoncoffee.com at 2.6 s2.6 s
  8. nmpinoncoffee.com at 3.0 s3.0 s

Speed

8 to fix58
  • Reduce unused JavaScript

    2.7 s · 488 KiB

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

  • Mobile performance score: 58

    58/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Stamped.io and Adroll and others), adding 1.8 MB and 575 ms of main-thread time.

  • Render-blocking requests

    750 ms

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

  • 1,882 HTML elements

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

  • Stamped.io adds 136 ms

    136 ms

    Stamped.io costs a phone 136 ms of main-thread work and 500 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.

  • Shopify adds 55 ms

    55 ms

    Shopify costs a phone 55 ms of main-thread work and 745 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.

  • LoyaltyLion adds 85 ms

    85 ms

    LoyaltyLion costs a phone 85 ms of main-thread work and 354 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.

  • Reduce unused CSS

    150 ms · 44 KiB

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

  • Improve image delivery

    181 KiB

    6 images could be 181 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 3 long tasks on the main thread

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

  • Use efficient cache lifetimes

    63 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

2 checks passed
  • Main-thread work: 2.0 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 16.6 s

    16.6 s

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

  • Time to Interactive: 16.8 s

    16.8 s

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

  • Speed Index: 7.5 s

    7.5 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 34 images without width and height

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

  • Total Blocking Time: 306 ms

    306 ms

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

  • Tap response (INP) held steady for real visitors

    -8%

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

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

    1.6 s

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

  • Real-user INP: 83 ms

    83 ms

    Real visitors wait 83 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.1 s

    1.1 s

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

  • Real-user TTFB: 550 ms

    550 ms

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

  • Largest content (LCP) got 24% faster for real visitors

    -24%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.2 s to 0.9 s 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

3 to fix69
  • Page weight: 3.5 MB in 371 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 371 requests on a phone: images 1.1 MB (59), scripts 1.1 MB (98) and other files 917 KiB (177). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    NMPC_30ct-k-cup_Variety-latteback_a4bf86ee-563d-48c1-9f75-23 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).

  • 3 images far larger than shown

    424 KiB

    3 images are downloaded at several times the size a phone draws them, for example 360650_8559857467682.png at 700 px wide, shown at 50 px. Resized copies would save about 424 KiB.

  • 2 images in older formats

    2 images (403 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 1.0 g of CO₂ per visit

    0.99 g

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

Accessibility

4 to fixGoogle 8894
  • 16 text elements with low contrast

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

  • 6 images without alt text

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

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

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

  • 4 links without text

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • Meta description is short (67 characters)

    Your meta description is only 67 characters: “Roasting Great Piñon Coffee in the Heart of the Southwest Since ‘94”. 70 to 160 characters is enough to sell the click.

  • One H1 headline

    Your <h1> is empty.

  • 61 internal links, 13 external

    The homepage links to 61 pages on nmpinoncoffee.com and 13 external pages.

6 checks passed
  • Title: 61 characters

    Your title is a healthy 61 characters: “Buy New Mexico Piñon Coffee Online & Albuquerque Coffee Shops”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    48%

    The HTML your server sends has 456 of the 947 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • llms.txt published

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://nmpinoncoffee.com/collections/flavored-coffee, https://nmpinoncoffee.com/collections/unflavored-coffee, https://nmpinoncoffee.com/collections/single-serve-pods, https://nmpinoncoffee.com/collections/cold-brew, https://nmpinoncoffee.com/collections/merch and https://nmpinoncoffee.com/collections/brewing-supplies and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://nmpinoncoffee.com/pages/community-donation-request has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://nmpinoncoffee.com/pages/rewards-2e02fe has 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 29 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

3 to fixGoogle 7776
  • 3 broken images

    3 images failed to load on a phone, for example https://d.adroll.com/uev/BE647UAGOFHDDOODAZAUTM/CXHIWOSVBNE5HIWBSPBYUR/?adroll_tpc=lx3%3Dlex-875dcf7e-8824-4efd-8dd5-36b3b8e5e127&af0=0fe6f973&adroll_fpc=73687efe5a2aa020b58a7e23c242a8aa-1794032919871.

  • 15 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 947 words of copy

    The homepage carries about 947 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 11 calls to action

    The homepage has 11 calls to action, for example “Shop”, “Community Donation Request” 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.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and The Trade Desk (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies (measured from a US location before any click).

  • 29 other companies contacted

    Loading the homepage contacts 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

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

Apps on your store

No apps were seen in the code your storefront loads.

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on nmpinoncoffee.com, including 14 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