Website review, no card needed

lvsouvenirshow.com logo

lvsouvenirshow.com website review

Visit site (opens in a new tab)Reviewed 20 November 202634 issues · 78 checks

This review found 34 issues worth fixing on lvsouvenirshow.com, 9 of them high impact, across 78 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
3.0 s1.8 sMay 30Nov 72.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.2 s
Jun 6, 20262.1 s
Jun 13, 20262.2 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20262.0 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.6 s
Aug 15, 20262.7 s
Aug 22, 20262.8 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.9 s
Sep 19, 20262.8 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.2 s
Oct 31, 20262.1 s
Nov 7, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
251 ms123 msJun 20Oct 31154 ms
Show as table
DateReal-visitor tap response (INP)
Jun 20, 2026138 ms
Jul 11, 2026144 ms
Jul 18, 2026156 ms
Jul 25, 2026150 ms
Aug 1, 2026160 ms
Aug 8, 2026189 ms
Aug 15, 2026203 ms
Aug 22, 2026227 ms
Aug 29, 2026236 ms
Sep 5, 2026227 ms
Sep 12, 2026230 ms
Sep 19, 2026225 ms
Sep 26, 2026219 ms
Oct 3, 2026210 ms
Oct 10, 2026172 ms
Oct 17, 2026170 ms
Oct 24, 2026162 ms
Oct 31, 2026154 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 lvsouvenirshow.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix56
  • Use efficient cache lifetimes

    2.4 s · 807 KiB

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

  • Reduce unused JavaScript

    1.4 s · 655 KiB

    About 655 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Render-blocking requests

    1.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and asp.events and others), adding 3.9 MB and 1.4 s of main-thread time.

  • Reduce unused CSS

    920 ms · 164 KiB

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

  • Google Tag Manager adds 910 ms

    910 ms

    Google Tag Manager costs a phone 910 ms of main-thread work and 1,000 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.

  • Mobile performance score: 56

    56/100

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

  • Improve image delivery

    300 ms · 281 KiB

    6 images could be 281 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • asp.events adds 136 ms

    136 ms

    asp.events costs a phone 136 ms of main-thread work and 2.3 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.

  • Main-thread work: 3.6 s

    A phone's processor spends 3.6 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • VWO adds 36 ms

    36 ms

    VWO costs a phone 36 ms of main-thread work and 301 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.

  • 15 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 80 ms

    80 ms

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

Core Web Vitals

6 to fix53
  • Largest Contentful Paint: 15.1 s

    15.1 s

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

  • Time to Interactive: 20.7 s

    20.7 s

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

  • Speed Index: 5.7 s

    5.7 s

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

  • Total Blocking Time: 491 ms

    491 ms

    Scripts block taps and scrolling for 491 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • 3 images without width and height

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

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

    +12%

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

  • Largest content (LCP) got 14% slower for real visitors

    +14%

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

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

1 checks passed
  • Cumulative Layout Shift: 0.011

    0.011

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

Images and page weight

4 to fix52
  • Page weight: 4.1 MB in 113 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 113 requests on a phone: images 1.6 MB (32), scripts 1.5 MB (39) and fonts 579 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    filters:no_upscale() is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 4 images far larger than shown

    312 KiB

    4 images are downloaded at several times the size a phone draws them, for example filters:no_upscale() at 1,024 px wide, shown at 198 px. Resized copies would save about 312 KiB.

  • 4 images below the first screen load straight away

    4 images further down the page (456 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.16 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 9694
  • 3 text elements with low contrast

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

  • Interactive controls must not be nested (3 elements)

    Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • Structured data has 1 problem

    Structured data found (Event, FAQPage, Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://lvsouvenirshow.com/includes/images/profiles/ico_group.png")”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 92 internal links, 20 external

    The homepage links to 92 pages on lvsouvenirshow.com and 20 external pages.

7 checks passed
  • Meta description: 93 characters

    Your meta description is 93 characters: “Join us October 6-8, 2027, at the must-attend event for the souvenir, resort & gift industry.”.

  • One H1 headline

    Your main headline reads: “The Must-Attend Event for the Souvenir, Resort & Gift Industry”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Welcome | Las Vegas Souvenir & Resort Gift Show 2027”.

  • Canonical URL set

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

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing url, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://lvsouvenirshow.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.

2 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 (1,484 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • 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.

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

    The homepage carries about 812 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “Event Schedule”, “LEARN MORE (opens in a new tab)” and “How do I Register?”.

  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 37 testimonial or review blocks and 1 customer or partner logo.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Opening hours shown

    Your opening hours are on the homepage.

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, LinkedIn Insight and Meta Pixel (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.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 cookies, 1 of them by other companies (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.

  • 26 other companies contacted

    Loading the homepage contacts 26 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 lvsouvenirshow.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
SHOWOFF by ASP.events
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 34 issues on lvsouvenirshow.com, including 17 speed issues, 2 SEO issues and 4 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