Website review, no card needed
bevtechonline.com website review
Visit site (opens in a new tab)Reviewed 21 November 202635 issues · 66 checks
This review found 35 issues worth fixing on bevtechonline.com, 13 of them high impact, across 66 checks. The most urgent: reduce unused JavaScript. 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
69D- #107,859 of 125,932 reviewed websitesbeats 12%
- #64,452 of 70,307 online storesbeats 7%
- #59,376 of 63,856 Shopify storesbeats 6%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 7.1 s |
| Jun 6, 2026 | 6.8 s |
| Jun 13, 2026 | 6.5 s |
| Jun 20, 2026 | 6.2 s |
| Jun 27, 2026 | 6.3 s |
| Jul 4, 2026 | 6.5 s |
| Jul 11, 2026 | 6.4 s |
| Jul 18, 2026 | 6.3 s |
| Jul 25, 2026 | 6.3 s |
| Aug 1, 2026 | 6.3 s |
| Aug 8, 2026 | 6.2 s |
| Aug 15, 2026 | 6.0 s |
| Aug 22, 2026 | 5.5 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 5.0 s |
| Sep 12, 2026 | 4.9 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.6 s |
| Oct 17, 2026 | 4.6 s |
| Oct 24, 2026 | 4.7 s |
| Oct 31, 2026 | 4.7 s |
| Nov 7, 2026 | 4.8 s |
| Nov 14, 2026 | 4.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 199 ms |
| Jun 6, 2026 | 203 ms |
| Jun 13, 2026 | 212 ms |
| Jun 20, 2026 | 217 ms |
| Jun 27, 2026 | 224 ms |
| Jul 4, 2026 | 232 ms |
| Jul 11, 2026 | 229 ms |
| Jul 18, 2026 | 232 ms |
| Jul 25, 2026 | 232 ms |
| Aug 1, 2026 | 221 ms |
| Aug 8, 2026 | 213 ms |
| Aug 15, 2026 | 221 ms |
| Aug 22, 2026 | 213 ms |
| Aug 29, 2026 | 213 ms |
| Sep 5, 2026 | 221 ms |
| Sep 12, 2026 | 211 ms |
| Sep 19, 2026 | 221 ms |
| Sep 26, 2026 | 221 ms |
| Oct 3, 2026 | 231 ms |
| Oct 10, 2026 | 229 ms |
| Oct 17, 2026 | 227 ms |
| Oct 24, 2026 | 229 ms |
| Oct 31, 2026 | 213 ms |
| Nov 7, 2026 | 229 ms |
| Nov 14, 2026 | 237 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.8 s · 525 KiBAbout 525 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.8 s faster on a phone.
Avoid multiple page redirects
1.7 sThe page goes through 3 redirects before it starts loading, costing about 1.7 s. Link and advertise the final URL directly.
Render-blocking requests
1.1 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.1 s.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
300 ms · 398 KiB4 files are served with short cache lifetimes, so returning visitors download them again (398 KiB).
Document request latency
450 ms · 44 KiBThe HTML itself could arrive about 450 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce unused CSS
300 ms · 57 KiBAbout 57 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Maps adds 178 ms
178 msGoogle Maps costs a phone 178 ms of main-thread work and 394 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.
7 third-party services on the page
7 third-party services load with your homepage (Google Maps, Google Tag Manager and Auth0 and others), adding 920 KiB and 370 ms of main-thread time.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 214 ms. During a long task the page ignores taps.
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: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 364 ms of it running JavaScript. That is comfortably low.
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.5 s
9.5 sYour largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Odeko”.
First Contentful Paint: 5.2 s
5.2 sThe first text or image appears after 5.2 s on a phone. Good is under 1.8 s.
Time to Interactive: 9.5 s
9.5 sThe page becomes fully interactive after 9.5 s. Good is under 3.8 s.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 389 ms
389 msScripts block taps and scrolling for 389 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) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 199 ms to 237 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 87 ms
87 msReal visitors wait 87 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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 730 ms
730 msReal visitors wait 730 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 30% faster for real visitors
-30%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 7.1 s to 4.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.37 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.37 g of CO₂e: 44.5 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.3 MB in 24 requests
1.3 MBYour homepage downloads 1.3 MB in 24 requests on a phone: scripts 934 KiB (9), images 217 KiB (2) and stylesheets 82 KiB (3). 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
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.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 2 failed. 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.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (5 characters)
Your title is only 5 characters: “Odeko”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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 XML sitemap
No XML sitemap at https://portal.odeko.com/sitemap.xml, so Google discovers your pages only by following links.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
1 checks passed
robots.txt in place
robots.txt is in place.
AI search readiness
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.
No llms.txt
There is no https://portal.odeko.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 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.
Best practices
2 small tap targets
2 of 6 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) InvalidValueError: initGoogleMapsPlaces is not a function”.
1 checks passed
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 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.
Only about 20 words
The homepage has only about 20 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
1 short form
A short form (0 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Cloudflare Web Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
11 other companies contacted
Loading the homepage contacts 11 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 bevtechonline.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
- Analytics
- Google Analytics
- Hosting
- CloudFront
Company
- Headquarters
- Aurora
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on bevtechonline.com, including 14 speed issues, 9 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.