Website review, no card needed
otgcoffee.com website review
Visit site (opens in a new tab)Reviewed 25 October 202624 issues · 73 checks
This review found 24 issues worth fixing on otgcoffee.com, 8 of them high impact, across 73 checks. The most urgent: 5,428 HTML elements. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83B- #27,433 of 119,930 reviewed websitesbeats 72%
- #18,067 of 67,979 online storesbeats 67%
- #17,512 of 61,955 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 988 ms |
| May 9, 2026 | 996 ms |
| May 16, 2026 | 977 ms |
| May 23, 2026 | 941 ms |
| May 30, 2026 | 933 ms |
| Jun 6, 2026 | 935 ms |
| Jun 13, 2026 | 951 ms |
| Jun 20, 2026 | 958 ms |
| Jun 27, 2026 | 976 ms |
| Jul 4, 2026 | 979 ms |
| Jul 11, 2026 | 984 ms |
| Jul 18, 2026 | 971 ms |
| Jul 25, 2026 | 960 ms |
| Aug 1, 2026 | 915 ms |
| Aug 8, 2026 | 892 ms |
| Aug 15, 2026 | 917 ms |
| Aug 22, 2026 | 917 ms |
| Aug 29, 2026 | 923 ms |
| Sep 5, 2026 | 906 ms |
| Sep 12, 2026 | 888 ms |
| Sep 19, 2026 | 869 ms |
| Sep 26, 2026 | 862 ms |
| Oct 3, 2026 | 878 ms |
| Oct 10, 2026 | 878 ms |
| Oct 17, 2026 | 854 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 87 ms |
| May 9, 2026 | 84 ms |
| May 16, 2026 | 79 ms |
| May 23, 2026 | 79 ms |
| May 30, 2026 | 79 ms |
| Jun 6, 2026 | 81 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 89 ms |
| Jun 27, 2026 | 95 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 95 ms |
| Jul 25, 2026 | 92 ms |
| Aug 1, 2026 | 92 ms |
| Aug 8, 2026 | 87 ms |
| Aug 15, 2026 | 88 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 79 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 72 ms |
| Sep 19, 2026 | 71 ms |
| Sep 26, 2026 | 72 ms |
| Oct 3, 2026 | 74 ms |
| Oct 10, 2026 | 75 ms |
| Oct 17, 2026 | 78 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
Speed
5,428 HTML elements
The page has 5,428 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 80
80/100Your mobile performance score is 80 (desktop: 97). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
80 KiB5 images could be 80 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 59 ms. During a long task the page ignores taps.
Render-blocking requests
50 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 50 ms.
2 third-party services on the page
2 third-party services load with your homepage (Shopify and shop.app), adding 65 KiB and 24 ms of main-thread time.
Use efficient cache lifetimes
5 KiB3 files are served with short cache lifetimes, so returning visitors download them again (5 KiB).
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.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 363 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.4 s
4.4 sYour 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 image.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 4.5 s
4.5 sThe page becomes fully interactive after 4.5 s. Good is under 3.8 s.
10 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.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 80 ms
80 msReal visitors wait 80 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 532 ms
532 msReal visitors wait 532 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 87 ms to 78 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 6 ms
6 msScripts block the page for only 6 ms while loading. Good is under 200 ms.
Images and page weight
About 0.5 g of CO₂ per visit
0.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.45 g of CO₂e: 54.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.6 MB in 199 requests
1.6 MBYour homepage downloads 1.6 MB in 199 requests on a phone: other files 885 KiB (122), images 377 KiB (7) and scripts 215 KiB (42). That is a lean page.
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
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 7 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (27 characters)
Your title is only 27 characters: “ON THE GRIND – On The Grind”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
One H1 headline
Your <h1> is empty.
23 internal links, 1 external
The homepage links to 23 pages on otgcoffee.com and 1 external page.
4 checks passed
Canonical URL set
The canonical URL is https://otgcoffee.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://otgcoffee.com/sitemap.xml.
AI search readiness
4 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,995 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://otgcoffee.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://otgcoffee.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://otgcoffee.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://otgcoffee.com/collections/all, https://otgcoffee.com/customer_authentication/redirect and https://otgcoffee.com/pages/locations-1 have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://otgcoffee.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 8 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.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
9 of 9 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 236 words
The homepage has only about 236 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.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact Us”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 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.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 otgcoffee.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
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on otgcoffee.com, including 6 speed issues, 5 SEO issues and 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.