Website review, no card needed

zillionsgift.com logo

zillionsgift.com website review

Visit site (opens in a new tab)Reviewed 11 October 202649 issues · 89 checks

This review found 49 issues worth fixing on zillionsgift.com, 19 of them high impact, across 89 checks. The most urgent: improve image delivery. 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.9 s1.7 sApr 18Oct 31.7 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.9 s
Apr 25, 20261.8 s
May 2, 20261.8 s
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
128 ms117 msApr 18Oct 3119 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026121 ms
Apr 25, 2026121 ms
May 2, 2026121 ms
May 9, 2026121 ms
May 16, 2026121 ms
May 23, 2026121 ms
May 30, 2026121 ms
Jun 6, 2026122 ms
Jun 13, 2026125 ms
Jun 20, 2026127 ms
Jun 27, 2026123 ms
Jul 4, 2026121 ms
Jul 11, 2026121 ms
Jul 18, 2026120 ms
Jul 25, 2026120 ms
Aug 1, 2026120 ms
Aug 8, 2026120 ms
Aug 15, 2026120 ms
Aug 22, 2026119 ms
Aug 29, 2026119 ms
Sep 5, 2026119 ms
Sep 12, 2026119 ms
Sep 19, 2026118 ms
Sep 26, 2026119 ms
Oct 3, 2026119 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 zillionsgift.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. zillionsgift.com at 1.0 s1.0 s
  2. zillionsgift.com at 2.0 s2.0 s
  3. zillionsgift.com at 3.0 s3.0 s
  4. zillionsgift.com at 4.0 s4.0 s
  5. zillionsgift.com at 5.0 s5.0 s
  6. zillionsgift.com at 6.0 s6.0 s
  7. zillionsgift.com at 7.0 s7.0 s
  8. zillionsgift.com at 8.0 s8.0 s

Speed

15 to fix30
  • Improve image delivery

    2.1 s · 467 KiB

    2 images could be 467 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

  • Use efficient cache lifetimes

    1.4 s · 1.1 MB

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

  • Render-blocking requests

    1.8 s

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

  • thegiftcardshop.com adds 1.3 s

    1.3 s

    thegiftcardshop.com costs a phone 1.3 s of main-thread work and 257 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 CSS

    1.0 s · 129 KiB

    About 129 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.0 s faster on a phone.

  • hcaptcha.com adds 1.1 s

    1.1 s

    hcaptcha.com costs a phone 1.1 s of main-thread work and 954 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.

  • Main-thread work: 10.3 s

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

  • Mobile performance score: 30

    30/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (thegiftcardshop.com, hcaptcha.com and InAuth and others), adding 3.4 MB and 4.0 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Reduce unused JavaScript

    300 ms · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • InAuth adds 920 ms

    920 ms

    InAuth costs a phone 920 ms of main-thread work and 37 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

    600 ms · 250 KiB

    250 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 370 ms

    370 ms

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

  • glassboxcdn.com adds 201 ms

    201 ms

    glassboxcdn.com costs a phone 201 ms of main-thread work and 480 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.

  • Font display

    100 ms

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

  • Legacy JavaScript

    69 KiB

    Polyfills for old browsers add 69 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: 13 ms

    13 ms

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

Core Web Vitals

11 to fix67
  • 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: 10.3 s

    10.3 s

    Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Skip to Content Toggle Nav Track Order Redeem for eGifts an…”.

  • Time to Interactive: 33.7 s

    33.7 s

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

  • Total Blocking Time: 3.3 s

    3.3 s

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

  • Speed Index: 12.6 s

    12.6 s

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

  • Real-user CLS: 0.11

    0.11

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Cumulative Layout Shift: 0.104

    0.104

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

  • 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) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

2 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 184 ms

    184 ms

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

Images and page weight

3 to fix45
  • Page weight: 5.7 MB in 328 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 328 requests on a phone: scripts 3.0 MB (260), images 1.9 MB (25) and HTML 468 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    InComm_Payments_Logo_HRZ_CMYK-LRG.jpg weighs 965 KiB. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

    2 images (1.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 1.6 g of CO₂ per visit

    1.60 g

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

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

5 to fixGoogle 8993
  • Hidden but focusable

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

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • 3 images without alt text

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

8 to fixGoogle 9262
  • No H1 headline

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

  • Title is short (4 characters)

    Your title is only 4 characters: “Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (230 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://zillionsgift.com/sitemap.xml, so Google discovers your pages only by following links.

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

  • 13 internal links, 4 external

    The homepage links to 13 pages on zillionsgift.com and 4 external pages.

1 checks passed
  • robots.txt in place

    robots.txt is in place.

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://zillionsgift.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 (307 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 5 pages without an H1

    https://zillionsgift.com/trackorder, https://zillionsgift.com/help, https://zillionsgift.com/sitemap, https://zillionsgift.com/important-documents and https://zillionsgift.com/terms have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 internal pages checked

    We fetched 7 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 7 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 7 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

3 to fixGoogle 6985
  • 5 small tap targets

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

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“`StorageType.persistent` is deprecated. Please use standardized `navigator.storage` instead.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'TenantFeatures')”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 236 words

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Track Order”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Track Order”, “Where to Buy” and “Contact Customer Care”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 32 cookies set on arrival

    32

    Opening the homepage sets 32 cookies (measured from a US location before any click).

  • 18 other companies contacted

    Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on zillionsgift.com, including 26 speed issues, 8 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