Website review, no card needed

verticurl.com logo

verticurl.com website review

Visit site (opens in a new tab)Reviewed 18 November 202629 issues · 75 checks

This review found 29 issues worth fixing on verticurl.com, 13 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. 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
5.0 s3.7 sMay 30Nov 144.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.8 s
Jun 6, 20264.7 s
Jun 13, 20264.6 s
Jun 20, 20264.6 s
Jun 27, 20264.7 s
Jul 4, 20264.8 s
Jul 11, 20264.8 s
Jul 18, 20264.6 s
Jul 25, 20264.4 s
Aug 1, 20263.8 s
Aug 8, 20263.9 s
Aug 15, 20264.0 s
Aug 22, 20263.8 s
Aug 29, 20263.9 s
Sep 5, 20264.1 s
Sep 12, 20264.1 s
Sep 19, 20264.2 s
Sep 26, 20264.5 s
Oct 3, 20264.5 s
Oct 10, 20264.6 s
Oct 17, 20264.8 s
Oct 24, 20264.7 s
Oct 31, 20264.4 s
Nov 7, 20264.2 s
Nov 14, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
153 ms110 msMay 30Nov 14136 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026141 ms
Jun 6, 2026137 ms
Jun 13, 2026148 ms
Jun 20, 2026145 ms
Jun 27, 2026144 ms
Jul 4, 2026145 ms
Jul 11, 2026133 ms
Jul 18, 2026128 ms
Jul 25, 2026127 ms
Aug 1, 2026115 ms
Aug 8, 2026126 ms
Aug 15, 2026127 ms
Aug 22, 2026123 ms
Aug 29, 2026129 ms
Sep 5, 2026121 ms
Sep 12, 2026120 ms
Sep 19, 2026121 ms
Sep 26, 2026123 ms
Oct 3, 2026137 ms
Oct 10, 2026137 ms
Oct 17, 2026133 ms
Oct 24, 2026133 ms
Oct 31, 2026133 ms
Nov 7, 2026135 ms
Nov 14, 2026136 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 verticurl.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. verticurl.com at 1.0 s1.0 s
  2. verticurl.com at 1.9 s1.9 s
  3. verticurl.com at 2.9 s2.9 s
  4. verticurl.com at 3.8 s3.8 s
  5. verticurl.com at 4.8 s4.8 s
  6. verticurl.com at 5.7 s5.7 s
  7. verticurl.com at 6.7 s6.7 s
  8. verticurl.com at 7.6 s7.6 s

Speed

5 to fix56
  • Use efficient cache lifetimes

    1.2 s · 1.1 MB

    61 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • Render-blocking requests

    1.3 s

    12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.

  • Mobile performance score: 56

    56/100

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

  • Reduce unused JavaScript

    430 ms · 280 KiB

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

  • Google Tag Manager adds 276 ms

    276 ms

    Google Tag Manager costs a phone 276 ms of main-thread work and 468 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google Analytics and cdn-cookieyes.com and others), adding 537 KiB and 332 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 35 KiB

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

  • 3 long tasks on the main thread

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

  • Improve image delivery

    42 KiB

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

  • Minify JavaScript

    16 KiB

    16 KiB could be saved by minifying JavaScript.

  • 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: 1.0 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

10 to fix0
  • 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.

  • Real-user LCP: 4.3 s

    4.3 s

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

  • Real-user CLS: 0.45

    0.45

    For real visitors the layout shifts by 0.45 (75th percentile). Good is under 0.1.

  • Real-user FCP: 4.0 s

    4.0 s

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

  • Speed Index: 10.7 s

    10.7 s

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

  • Cumulative Layout Shift: 0.363

    0.363

    The layout shifts by 0.363 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 8.8 s

    8.8 s

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

  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your 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 element shown below. Most of its time is resource load delay (4.9 s).

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 17 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

2 checks passed
  • Largest content (LCP) got 12% faster for real visitors

    -12%

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

  • Total Blocking Time: 97 ms

    97 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.2 MB in 86 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 86 requests on a phone: media 983 KiB (1), scripts 772 KiB (23) and fonts 220 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (31 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.62 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 8795
  • Input buttons must have discernible text (1 element)

    Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

  • 4 text elements with low contrast

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

  • 2 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 30 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10087
  • 4 H1 headlines

    There are 4 <h1> headlines (“The gap between your marketing vision and technic…”, “Your martech stack is the bottleneck. We make it …” and “Your loyalty program is a cost center. We make it…”). One clear main headline is easier for people and search engines.

  • Meta description is long (175 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 25 internal links, 26 external

    The homepage links to 25 pages on verticurl.com and 26 external pages.

5 checks passed
  • Title: 58 characters

    Your title is a healthy 58 characters: “Marketing and Demand Generation Agency for B2B, B2C & CTOs”.

  • Canonical URL set

    The canonical URL is https://www.verticurl.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage 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://www.verticurl.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix88
  • 2 linked pages hidden from search

    https://www.verticurl.com/terms-of-usage and https://www.verticurl.com/privacy-policy are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 7 pages without a meta description

    https://www.verticurl.com/work/case-studies, https://www.verticurl.com/work/insights, https://www.verticurl.com/work/testimonials, https://www.verticurl.com/about/in-the-news, https://www.verticurl.com/contact and https://www.verticurl.com/terms-of-usage and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://www.verticurl.com/work/case-studies, https://www.verticurl.com/about/awards and https://www.verticurl.com/contact took over 3 s to send their HTML from our server.

  • 13 internal pages checked

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

5 checks passed
  • Linked pages load

    All 13 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8891
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “The Content-Security-Policy directive 'object-src' contains the keyword 'none' alongside with other source expressions.…”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

    The homepage carries about 476 words of visible text.

4 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact” and “Contact us today”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 15 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

  • 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). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 7 cookies set on arrival

    7

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

  • 6 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
AWS

Company

Headquarters
Atlanta

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on verticurl.com, including 15 speed issues, 3 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