Website review, no card needed

velvettaco.com logo

velvettaco.com website review

Visit site (opens in a new tab)Reviewed 27 October 202621 issues · 75 checks

This review found 21 issues worth fixing on velvettaco.com, 8 of them high impact, across 75 checks. The most urgent: render-blocking 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
1.6 s1.0 sMay 9Oct 241.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.6 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.4 s
Jun 13, 20261.3 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.3 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
163 ms77 msMay 9Oct 2487 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026146 ms
May 16, 2026148 ms
May 23, 2026151 ms
May 30, 2026153 ms
Jun 6, 2026147 ms
Jun 13, 2026136 ms
Jun 20, 2026120 ms
Jun 27, 202698 ms
Jul 4, 202688 ms
Jul 11, 202689 ms
Jul 18, 202689 ms
Jul 25, 202689 ms
Aug 1, 202689 ms
Aug 8, 202688 ms
Aug 15, 202688 ms
Aug 22, 202688 ms
Aug 29, 202688 ms
Sep 5, 202688 ms
Sep 12, 202689 ms
Sep 19, 202692 ms
Sep 26, 202692 ms
Oct 3, 202692 ms
Oct 10, 202691 ms
Oct 17, 202688 ms
Oct 24, 202687 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 velvettaco.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. velvettaco.com at 1.0 s1.0 s
  2. velvettaco.com at 2.0 s2.0 s
  3. velvettaco.com at 3.1 s3.1 s
  4. velvettaco.com at 4.1 s4.1 s
  5. velvettaco.com at 5.1 s5.1 s
  6. velvettaco.com at 6.1 s6.1 s
  7. velvettaco.com at 7.2 s7.2 s
  8. velvettaco.com at 8.2 s8.2 s

Speed

7 to fix42
  • Render-blocking requests

    3.1 s

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

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42 (desktop: 68). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused CSS

    610 ms · 97 KiB

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

  • Reduce unused JavaScript

    610 ms · 52 KiB

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

  • Minify CSS

    300 ms · 12 KiB

    12 KiB could be saved by minifying CSS.

  • 1 third-party service on the page

    1 third-party service load with your homepage (b-cdn.net), adding 1.2 MB and 172 ms of main-thread time.

  • b-cdn.net adds 172 ms

    172 ms

    b-cdn.net costs a phone 172 ms of main-thread work and 1.2 MB 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.

  • Improve image delivery

    160 KiB

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

  • 1 long task on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    11 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 68 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Minify JavaScript

    9 KiB

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

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

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

  • Server response: 54 ms

    54 ms

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

Core Web Vitals

8 to fix100
  • 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: 7.8 s

    7.8 s

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

  • Cumulative Layout Shift: 0.772

    0.772

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Time to Interactive: 7.9 s

    7.9 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Speed Index: 4.7 s

    4.7 s

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

  • 15 images without width and height

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

7 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 78 ms

    78 ms

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

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

    1.7 s

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

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

    -40%

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

  • Largest content (LCP) got 20% faster for real visitors

    -20%

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

  • 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

100
  • About 0.4 g of CO₂ per visit

    0.36 g

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

    1.3 MB

    Your homepage downloads 1.3 MB in 51 requests on a phone: images 676 KiB (12), fonts 274 KiB (5) and scripts 191 KiB (18). 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

Google 100100
2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • 2 H1 headlines

    There are 2 <h1> headlines (“Get the Mobile App” and “Leaving velvettaco.com”). One clear main headline is easier for people and search engines.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 33 internal links, 28 external

    The homepage links to 33 pages on velvettaco.com and 28 external pages.

7 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Dine-In, Delivery & Take-Out Available! Featuring a variety of globally inspired tacos made in-house with fresh local i…”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “You've Never Had a Taco Like This | Velvet Taco”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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.velvettaco.com/sitemap_index.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: 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 (719 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 9 pages without a meta description

    https://www.velvettaco.com/wtf-weekly-taco-feature, https://www.velvettaco.com/catering, https://www.velvettaco.com/the-velvet-room, https://www.velvettaco.com/gift-cards, https://www.velvettaco.com/careers and https://www.velvettaco.com/international-partner and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 6 small tap targets

    6 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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.

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

  • About 372 words of copy

    The homepage carries about 372 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “ORDER NOW” and “ORDER CATERING”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Order Now”, “Order Catering” and “Learn More”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

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

  • 2 other companies contacted

    Loading the homepage contacts 2 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 velvettaco.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
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on velvettaco.com, including 15 speed issues, 2 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