Website review, no card needed

ignitedusa.com logo

ignitedusa.com website review

Visit site (opens in a new tab)Reviewed 19 October 202633 issues · 56 checks

This review found 33 issues worth fixing on ignitedusa.com, 17 of them high impact, across 56 checks. The most urgent: unpkg adds 4.1 s. 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 ignitedusa.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ignitedusa.com at 1.1 s1.1 s
  2. ignitedusa.com at 2.2 s2.2 s
  3. ignitedusa.com at 3.3 s3.3 s
  4. ignitedusa.com at 4.4 s4.4 s
  5. ignitedusa.com at 5.5 s5.5 s
  6. ignitedusa.com at 6.6 s6.6 s
  7. ignitedusa.com at 7.6 s7.6 s
  8. ignitedusa.com at 8.7 s8.7 s

Speed

11 to fix19
  • Unpkg adds 4.1 s

    4.1 s

    Unpkg costs a phone 4.1 s of main-thread work and 897 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused JavaScript

    3.1 s · 635 KiB

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

  • Render-blocking requests

    2.3 s

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

  • Mobile performance score: 19

    19/100

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

  • Main-thread work: 9.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Unpkg, Google Tag Manager and lfeeder.com and others), adding 1.6 MB and 5.1 s of main-thread time.

  • Improve image delivery

    4.0 MB

    3 images could be 4.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 698 ms

    698 ms

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

  • Minify JavaScript

    450 ms · 119 KiB

    119 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    450 ms · 93 KiB

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

  • Legacy JavaScript

    50 ms · 26 KiB

    Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

  • 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: 1 ms

    1 ms

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

Core Web Vitals

7 to fix23
  • Largest Contentful Paint: 13.7 s

    13.7 s

    Your largest element takes 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your brand deserves more than a marketing agency. It deserv…”. Most of its time is element render delay (7.3 s).

  • Time to Interactive: 29.9 s

    29.9 s

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

  • Total Blocking Time: 3.4 s

    3.4 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Speed Index: 10.4 s

    10.4 s

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

  • 51 images without width and height

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

  • Cumulative Layout Shift: 0.184

    0.184

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

  • 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: 12.5 MB in 106 requests

    12.5 MB

    Your homepage downloads 12.5 MB in 106 requests on a phone: images 9.3 MB (59), scripts 1.5 MB (14) and media 1.5 MB (1). Under 2 MB keeps phones on slow connections fast.

  • About 3.6 g of CO₂ per visit

    3.55 g

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

Accessibility

4 to fixGoogle 8992
  • 47 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

    All page content should be contained by landmarks: 114 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.

1 checks passed
  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 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

3 to fixGoogle 10083
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (190 characters)

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

6 checks passed
  • Title: 53 characters

    Your title is a healthy 53 characters: “Ignited — Lighting the Way | Brand & Marketing Agency”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization 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://ignitedusa.com/sitemap.xml.

AI search readiness

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.

  • llms.txt published

    The site publishes https://ignitedusa.com/llms.txt (2 KiB, 6 links), a plain-text guide to the site for AI tools.

Best practices

1 to fixGoogle 10092
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

  • Only about 0 words

    The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies (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.

  • 16 other companies contacted

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

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on ignitedusa.com, including 18 speed issues, 3 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