Website review, no card needed

evogimbals.com logo

evogimbals.com website review

Visit site (opens in a new tab)Reviewed 10 November 202626 issues · 81 checks

This review found 26 issues worth fixing on evogimbals.com, 10 of them high impact, across 81 checks. The most urgent: page weight: 11.1 MB in 352 requests. 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
4.1 s1.3 sMay 23Nov 71.7 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.0 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.7 s
Jun 27, 20263.2 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.8 s
Jul 25, 20263.7 s
Aug 1, 20261.9 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20261.8 s
Sep 26, 20261.6 s
Oct 3, 20261.8 s
Oct 10, 20262.7 s
Oct 17, 20262.8 s
Oct 24, 20262.7 s
Oct 31, 20262.5 s
Nov 7, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
701 ms83 msMay 23Nov 7242 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026230 ms
May 30, 2026242 ms
Jun 6, 2026222 ms
Jun 13, 2026163 ms
Jun 20, 2026154 ms
Jun 27, 2026400 ms
Jul 4, 2026623 ms
Jul 11, 2026623 ms
Jul 18, 2026625 ms
Jul 25, 2026630 ms
Aug 1, 2026163 ms
Aug 8, 2026173 ms
Aug 15, 2026179 ms
Aug 22, 2026205 ms
Aug 29, 2026208 ms
Sep 5, 2026216 ms
Sep 12, 2026238 ms
Sep 19, 2026154 ms
Oct 10, 2026374 ms
Oct 17, 2026422 ms
Oct 24, 2026437 ms
Oct 31, 2026419 ms
Nov 7, 2026242 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 evogimbals.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix79
  • 6,359 HTML elements

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

  • Mobile performance score: 79

    79/100

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

  • Render-blocking requests

    900 ms

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

  • Improve image delivery

    417 KiB

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

  • Main-thread work: 2.1 s

    A phone's processor spends 2.1 s on main-thread work while loading, 621 ms 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 (cloudfront.net, Shopify and klck.dev and others), adding 377 KiB and 201 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 27 KiB

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

  • 1 long task on the main thread

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

  • Reduce unused JavaScript

    100 KiB

    About 100 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    20 KiB

    6 files are served with short cache lifetimes, so returning visitors download them again (20 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.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

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

5 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Largest Contentful Paint: 5.2 s

    5.2 s

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

  • Time to Interactive: 8.9 s

    8.9 s

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

  • Real-user INP: 242 ms

    242 ms

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

  • Tap response (INP) got 40% slower for real visitors

    +40%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

8 checks passed
  • 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 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.5 s

    1.5 s

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

  • Real-user TTFB: 633 ms

    633 ms

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

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.063

    0.063

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 29 ms

    29 ms

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

Images and page weight

1 to fix70
  • Page weight: 11.1 MB in 352 requests

    11.1 MB

    Your homepage downloads 11.1 MB in 352 requests on a phone: media 8.1 MB (1), other files 1.1 MB (189) and images 1.1 MB (33). Under 2 MB keeps phones on slow connections fast.

  • About 3.1 g of CO₂ per visit

    3.14 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.14 g of CO₂e: 376.4 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

6 to fixGoogle 8391
  • Hidden but focusable

    6 elements hidden from screen readers can still receive keyboard focus.

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

  • 2 images without alt text

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

  • 54 form fields without a label

    54 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 2 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 9289
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “EVO GimbalsⓇ Cutting Edge Camera Gear & Accessories – EVOGimbals.com”.

  • Structured data has 1 problem

    Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("www.evogimbals.com")”.

  • 146 internal links, 0 external

    The homepage links to 146 pages on evogimbals.com and 0 external pages.

6 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Professional Camera Stabilizers, 360 Cameras & Accessories | Located in Bend, Oregon | BEST Industry Support + US Warra…”.

  • One H1 headline

    Your main headline reads: “All Day. All Night. All Angles.”.

  • Canonical URL set

    The canonical URL is https://www.evogimbals.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://www.evogimbals.com/sitemap.xml.

AI search readiness

100
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: 5 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,682 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 6 pages without a meta description

    https://www.evogimbals.com/collections/360-cameras, https://www.evogimbals.com/collections/action-cameras, https://www.evogimbals.com/collections/insta360-accessories, https://www.evogimbals.com/collections/insta360-batteries-chargers, https://www.evogimbals.com/collections/insta360-cases and https://www.evogimbals.com/collections/insta360-dive-cases have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.evogimbals.com/pages/free-shipping-1, https://www.evogimbals.com/collections/360-cameras, https://www.evogimbals.com/products/insta360-x5-8k-360-action-camera-all-day-all-angle-shooting, https://www.evogimbals.com/products/insta360-x4, https://www.evogimbals.com/products/insta360-one-x3 and https://www.evogimbals.com/collections/action-cameras and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 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

    15 of 16 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 377 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”.

  • 1 call to action

    The homepage has 1 call to action, for example “Shop now”.

  • 6 short forms

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

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, Meta Pixel and Pinterest Tag (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.

  • 14 cookies set on arrival

    14

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

  • 27 other companies contacted

    Loading the homepage contacts 27 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 evogimbals.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 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Sales Discounts · Seo Manager Venntov · Judge Me Reviews · Pushowl · cloudfront.net · widgetic.com · oxiapps.com · buynowbutton.us · b-cdn.net · klck.dev

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

Company

Headquarters
Bend

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on evogimbals.com, including 10 speed issues, 2 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