Website review, no card needed

gtvapor.com logo

gtvapor.com website review

Visit site (opens in a new tab)Reviewed 5 November 202632 issues · 73 checks

This review found 32 issues worth fixing on gtvapor.com, 6 of them high impact, across 73 checks. The most urgent: 7 text elements with low contrast. 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 gtvapor.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix86
  • Mobile performance score: 86

    86/100

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

  • Render-blocking requests

    900 ms

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

  • Reduce unused CSS

    450 ms · 84 KiB

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

  • Minify CSS

    450 ms · 70 KiB

    70 KiB could be saved by minifying CSS.

  • Reduce unused JavaScript

    440 ms · 69 KiB

    About 69 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 440 ms faster on a phone.

  • Improve image delivery

    153 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google Fonts and others), adding 171 KiB and 77 ms of main-thread time.

  • Use efficient cache lifetimes

    87 KiB

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

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

1 checks passed
  • Main-thread work: 0.2 s

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

Core Web Vitals

4 to fix92
  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Speed Index: 4.6 s

    4.6 s

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

  • Largest Contentful Paint: 3.0 s

    3.0 s

    Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Check out one of our Traverse City locations for all your v…”. Most of its time is element render delay (2.4 s).

  • 2 images without width and height

    2 images 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.

3 checks passed
  • Time to Interactive: 3.0 s

    3.0 s

    The page is fully interactive after 3.0 s.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix90
  • 2 images far larger than shown

    115 KiB

    2 images are downloaded at several times the size a phone draws them, for example northSign.webp at 1,360 px wide, shown at 108 px. Resized copies would save about 115 KiB.

  • 1 image in older formats

    1 image (35 KiB) is 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 0.1 g of CO₂ per visit

    0.13 g

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

2 checks passed
  • Page weight: 488 KiB in 21 requests

    488 KiB

    Your homepage downloads 488 KiB in 21 requests on a phone: scripts 203 KiB (5), images 179 KiB (4) and stylesheets 101 KiB (9). That is a lean page.

  • Images load when needed

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

Accessibility

5 to fixGoogle 8890
  • 7 text elements with low contrast

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • Table header text should not be empty (2 elements)

    Table header text should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 23 automated accessibility rules passed

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

SEO

6 to fixGoogle 10067
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (15 characters)

    Your title is only 15 characters: “Home | GT Vapor”. 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.

  • Meta description is long (188 characters)

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

  • 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://gtvapor.com/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 12 internal links, 2 external

    The homepage links to 12 pages on gtvapor.com and 2 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://gtvapor.com/en.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • 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://gtvapor.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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.

Other pages

4 to fix81
  • 4 pages share 2 titles

    https://gtvapor.com/en/locations/traverse-city-north and https://gtvapor.com/locations/traverse-city-north all use the title “Traverse City North | GT Vapor”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages share a meta description

    https://gtvapor.com/en/locations, https://gtvapor.com/en/locations/traverse-city-north, https://gtvapor.com/en/locations/traverse-city-south, https://gtvapor.com/locations/traverse-city-north and https://gtvapor.com/locations/traverse-city-south use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://gtvapor.com/locations/traverse-city-north, whose canonical is https://gtvapor.com/en/locations/traverse-city-north. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    https://gtvapor.com/en/locations, https://gtvapor.com/en/locations/traverse-city-north, https://gtvapor.com/en/locations/traverse-city-south, https://gtvapor.com/locations/traverse-city-north and https://gtvapor.com/locations/traverse-city-south have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://gtvapor.com/en/locations, https://gtvapor.com/en/locations/traverse-city-north, https://gtvapor.com/en/locations/traverse-city-south, https://gtvapor.com/locations/traverse-city-north and https://gtvapor.com/locations/traverse-city-south 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.

  • 5 internal pages checked

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

4 checks passed
  • Linked pages load

    All 5 pages we checked loaded without an error.

  • Every page has a meta description

    All 5 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Only about 76 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

3 checks passed
  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 3 cookies set on arrival

    3

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

  • 4 other companies contacted

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

Upkeep, stack and company

Stack

CMS
GravCMS
Analytics
Google Analytics
Hosting
Cloudflare

Company

Headquarters
Cadillac

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

Go beyond the website

What your $25 Growth Playbook adds

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

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