Website review, no card needed

digimarconrockymountains.com logo

digimarconrockymountains.com website review

Visit site (opens in a new tab)Reviewed 11 November 202648 issues · 87 checks

This review found 48 issues worth fixing on digimarconrockymountains.com, 18 of them high impact, across 87 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

Full-page screenshot of digimarconrockymountains.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. digimarconrockymountains.com at 1.9 s1.9 s
  2. digimarconrockymountains.com at 3.8 s3.8 s
  3. digimarconrockymountains.com at 5.7 s5.7 s
  4. digimarconrockymountains.com at 7.6 s7.6 s
  5. digimarconrockymountains.com at 9.5 s9.5 s
  6. digimarconrockymountains.com at 11.4 s11.4 s
  7. digimarconrockymountains.com at 13.3 s13.3 s
  8. digimarconrockymountains.com at 15.2 s15.2 s

Speed

12 to fix25
  • Use efficient cache lifetimes

    3.6 s · 1.3 MB

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

  • Render-blocking requests

    3.5 s

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

  • Reduce unused JavaScript

    1.9 s · 865 KiB

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

  • Font display

    2.5 s

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

  • Mobile performance score: 25

    25/100

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

  • Main-thread work: 7.1 s

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

  • 4,620 HTML elements

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

  • 8 third-party services on the page

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

  • Reduce unused CSS

    600 ms · 170 KiB

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

  • Improve image delivery

    300 ms · 374 KiB

    3 images could be 374 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.

  • Google Tag Manager adds 578 ms

    578 ms

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

  • Vimeo adds 100 ms

    100 ms

    Vimeo costs a phone 100 ms of main-thread work and 516 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.

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 22 KiB

    22 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 20 KiB

    20 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    35 KiB

    Polyfills for old browsers add 35 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: 57 ms

    57 ms

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

Core Web Vitals

7 to fix29
  • Largest Contentful Paint: 15.4 s

    15.4 s

    Your largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Premier Digital Marketing, Media and Advertising Confer…”. Most of its time is element render delay (10.1 s).

  • Speed Index: 26.8 s

    26.8 s

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

  • Time to Interactive: 24.3 s

    24.3 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Total Blocking Time: 957 ms

    957 ms

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

  • Cumulative Layout Shift: 0.214

    0.214

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

  • 4 images without width and height

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

Images and page weight

1 to fix33
  • Page weight: 4.1 MB in 224 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 224 requests on a phone: scripts 2.2 MB (74), images 1.1 MB (68) and fonts 508 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.17 g

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

Accessibility

12 to fixGoogle 6260
  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 36 images without alt text

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

  • 15 buttons without a name

    15 buttons have no accessible name, so screen readers announce just “button”.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 117 text elements with low contrast

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

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • button, link, and menuitem elements do not have accessible names.

    button, link, and menuitem elements do not have accessible names. (2 elements).

  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

  • ARIA input fields do not have accessible names

    ARIA input fields do not have accessible names (1 element).

  • ARIA toggle fields do not have accessible names

    ARIA toggle fields do not have accessible names (1 element).

  • Headings skip levels

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

1 checks passed
  • 8 automated accessibility rules passed

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

SEO

6 to fixGoogle 7774
  • 42 links crawlers can't follow

    42 links have no real href, so search engines can't follow them.

  • Title is long (131 characters)

    Your title is 131 characters, so Google will cut it off around 60: “DigiMarCon Rocky Mountains 2026 · Salt Lake City, UT · November 12 - 13, 2026 · Digital M…”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Hurry, Limited Passes Remaining!” and “Choose your own experience”). One clear main headline is easier for people and search engines.

  • Meta description is long (439 characters)

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

  • Structured data has 2 problems

    Structured data found (BreadcrumbList, WebPage and WebSite) but with 2 problems, for example “ld+json block 2 is not valid JSON (Bad control character in string literal in JSON at position )”.

  • No social preview image

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

  • 235 internal links, 227 external

    The homepage links to 235 pages on digimarconrockymountains.com and 227 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://digimarconrockymountains.com/.

  • 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://digimarconrockymountains.com/sitemap.xml.

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://digimarconrockymountains.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.

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

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • 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 10 pages that loaded have a <title>.

Best practices

4 to fixGoogle 4685
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

  • 14 distorted images

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

  • 5 low-resolution images

    5 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 5 words

    The homepage has only about 5 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 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.

  • Urgency cues

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

4 checks passed
  • 89 calls to action

    The homepage has 89 calls to action, for example “Book an Exhibit Booth”, “Request an Exhibitor Prospectus” and “Join Next Exhibitor Overview Webinar”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 13 testimonial or review blocks, 16 customer or partner logos and “150,000+ members”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

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.

  • 1 other company contacted

    Loading the homepage contacts 1 host 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 digimarconrockymountains.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
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on digimarconrockymountains.com, including 19 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