Website review, no card needed

digimarconnevada.com logo

digimarconnevada.com website review

Visit site (opens in a new tab)Reviewed 9 November 202646 issues · 96 checks

This review found 46 issues worth fixing on digimarconnevada.com, 23 of them high impact, across 96 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
18.1 s3.0 sJul 25Nov 75.2 s
Show as table
DateReal-visitor load time (LCP)
Jul 25, 202616.3 s
Aug 1, 20267.0 s
Aug 8, 20265.7 s
Aug 15, 20265.1 s
Aug 22, 20265.1 s
Sep 12, 20264.8 s
Sep 19, 20264.7 s
Sep 26, 20264.8 s
Oct 10, 20265.0 s
Oct 17, 20266.2 s
Oct 24, 20265.9 s
Oct 31, 20265.3 s
Nov 7, 20265.2 s

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 digimarconnevada.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. digimarconnevada.com at 1.7 s1.7 s
  2. digimarconnevada.com at 3.3 s3.3 s
  3. digimarconnevada.com at 5.0 s5.0 s
  4. digimarconnevada.com at 6.6 s6.6 s
  5. digimarconnevada.com at 8.3 s8.3 s
  6. digimarconnevada.com at 9.9 s9.9 s
  7. digimarconnevada.com at 11.6 s11.6 s
  8. digimarconnevada.com at 13.3 s13.3 s

Speed

10 to fix45
  • Render-blocking requests

    3.5 s

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

  • Reduce unused JavaScript

    1.5 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 45

    45/100

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

  • Main-thread work: 4.5 s

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

  • 3,766 HTML elements

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

  • Use efficient cache lifetimes

    900 ms · 335 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Vimeo and others), adding 2.0 MB and 1.0 s of main-thread time.

  • Reduce unused CSS

    760 ms · 157 KiB

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

  • Google Tag Manager adds 292 ms

    292 ms

    Google Tag Manager costs a phone 292 ms of main-thread work and 473 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 158 ms

    158 ms

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

  • 13 long tasks on the main thread

    13 long tasks block the main thread while loading, the longest for 211 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).

  • Improve image delivery

    46 KiB

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

  • Legacy JavaScript

    35 KiB

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

  • Minify CSS

    10 ms · 20 KiB

    20 KiB could be saved by minifying CSS.

  • Minify JavaScript

    10 ms · 17 KiB

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

1 checks passed
  • Server response: 11 ms

    11 ms

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

Core Web Vitals

9 to fix50
  • 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: 8.3 s

    8.3 s

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

  • Real-user FCP: 3.6 s

    3.6 s

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

  • Real-user TTFB: 2.2 s

    2.2 s

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

  • Largest Contentful Paint: 13.0 s

    13.0 s

    Your largest element takes 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We have become aware of unauthorized emails circulating tha…”. Most of its time is element render delay (10.5 s).

  • Speed Index: 22.3 s

    22.3 s

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

  • Time to Interactive: 25.0 s

    25.0 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Total Blocking Time: 487 ms

    487 ms

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

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

    -55%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.2 MB in 199 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 199 requests on a phone: scripts 2.5 MB (75), images 897 KiB (41) and fonts 419 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.19 g

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

3 checks passed
  • 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

15 to fixGoogle 6279
  • 15 buttons without a name

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

  • 101 text elements with low contrast

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

  • 12 tap targets too small

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

  • ARIA commands must have an accessible name (2 elements)

    ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • ARIA toggle fields must have an accessible name (2 elements)

    ARIA toggle fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • Frames without titles

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

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 35 images without alt text

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

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

    All page content should be contained by landmarks: 167 elements on the page fail this check, rated moderate 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.

  • No main landmark

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

  • Zoom is disabled

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

  • 10 links without text

    10 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

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

  • Headings should not be empty (2 elements)

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

  • 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
  • 39 automated accessibility rules passed

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

SEO

4 to fixGoogle 7782
  • Title is long (127 characters)

    Your title is 127 characters, so Google will cut it off around 60: “DigiMarCon World 2026 · Las Vegas, NV · November 4 - 5, 2026 · Digital Marketing, Media a…”.

  • Meta description is long (416 characters)

    Your meta description is 416 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 )”.

  • 16 links crawlers can't follow

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

  • 105 internal links, 247 external

    The homepage links to 105 pages on digimarconnevada.com and 247 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Choose your own experience”.

  • Canonical URL set

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

  • No llms.txt

    There is no https://digimarconworld.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 (5,056 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 67 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5074
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17513376&tm=gtm002&Ver=2&mid=9c5cd53b-2645-46c6-b771-ceabaaadaccf&bo=1&sid=8f1f4030dc2111f1968d0bd785869d1f&vid=8f1f7020dc2111f1ba14131961a32103&vids=1&msclkid=N&pi=91.

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

  • 6 JavaScript errors while loading

    6 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 (Not Found)”.

  • 6 low-resolution images

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

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 2,610 words of copy

    The homepage carries about 2,610 words of visible text.

  • Urgency cues

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BUY TICKETS”.

  • 67 calls to action

    The homepage has 67 calls to action, for example “Request a Sponsorship Prospectus”, “Join Next Sponsorship Overview Webinar” and “CONTACT”.

  • 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

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, Meta Pixel and Microsoft Ads (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.

  • 18 cookies set on arrival

    18

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

  • 36 other companies contacted

    Loading the homepage contacts 36 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 digimarconnevada.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 46 issues on digimarconnevada.com, including 19 speed issues, 4 SEO issues and 1 conversion gap. 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