Website review, no card needed

prismplatinum.us logo

prismplatinum.us website review

Visit site (opens in a new tab)Reviewed 8 November 202640 issues · 86 checks

This review found 40 issues worth fixing on prismplatinum.us, 12 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. 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
2.0 s1.7 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
142 ms99 msMay 16Oct 31137 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026104 ms
May 23, 2026104 ms
May 30, 2026104 ms
Jun 6, 2026112 ms
Jun 13, 2026119 ms
Jun 20, 2026121 ms
Jun 27, 2026129 ms
Jul 4, 2026130 ms
Jul 11, 2026129 ms
Jul 18, 2026128 ms
Jul 25, 2026124 ms
Aug 1, 2026122 ms
Aug 8, 2026125 ms
Aug 15, 2026129 ms
Aug 22, 2026129 ms
Aug 29, 2026122 ms
Sep 5, 2026128 ms
Sep 12, 2026129 ms
Sep 19, 2026129 ms
Sep 26, 2026131 ms
Oct 3, 2026133 ms
Oct 10, 2026130 ms
Oct 17, 2026136 ms
Oct 24, 2026137 ms
Oct 31, 2026137 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 prismplatinum.us (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. prismplatinum.us at 0.7 s0.7 s
  2. prismplatinum.us at 1.5 s1.5 s
  3. prismplatinum.us at 2.2 s2.2 s
  4. prismplatinum.us at 3.0 s3.0 s
  5. prismplatinum.us at 3.7 s3.7 s
  6. prismplatinum.us at 4.5 s4.5 s
  7. prismplatinum.us at 5.2 s5.2 s
  8. prismplatinum.us at 6.0 s6.0 s

Speed

8 to fix65
  • Reduce unused JavaScript

    1.7 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.7 s faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 963 KiB

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

  • Mobile performance score: 65

    65/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (route.com, Shopify and Google Tag Manager and others), adding 1.6 MB and 743 ms of main-thread time.

  • Main-thread work: 3.5 s

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

  • 3 long tasks on the main thread

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

  • route.com adds 191 ms

    191 ms

    route.com costs a phone 191 ms of main-thread work and 542 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.

  • Shopify adds 143 ms

    143 ms

    Shopify costs a phone 143 ms of main-thread work and 646 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.

  • Render-blocking requests

    250 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.

  • Minify JavaScript

    150 ms · 22 KiB

    22 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    50 ms · 65 KiB

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

  • Improve image delivery

    107 KiB

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

  • Reduce unused CSS

    69 KiB

    About 69 KiB of CSS is downloaded but never applied on this page.

  • Font display

    50 ms

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

10 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: 15.8 s

    15.8 s

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

  • Time to Interactive: 22.3 s

    22.3 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

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

    +32%

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • Total Blocking Time: 207 ms

    207 ms

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

  • 2 images without width and height

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

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

    +11%

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

4 checks passed
  • Real-user INP: 128 ms

    128 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user TTFB: 668 ms

    668 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix64
  • Page weight: 4.5 MB in 299 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 299 requests on a phone: scripts 2.4 MB (128), images 1,014 KiB (34) and other files 802 KiB (118). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    1200_1600_A4_PtI_PtII_Purple_Pre-Order_Portrait_JPG_Shopify_ 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).

  • About 1.3 g of CO₂ per visit

    1.28 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 7989
  • 5 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • Zoom is disabled

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • ARIA role should be appropriate for the element (1 element)

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

  • Headings skip levels

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • Title is short (12 characters)

    Your title is only 12 characters: “ULTBIAS - US”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • 81 internal links, 18 external

    The homepage links to 81 pages on prismplatinum.us and 18 external pages.

6 checks passed
  • Meta description: 96 characters

    Your meta description is 96 characters: “ULTBIAS offer premium accessories to protect your photocard and TCG collections with confidence.”.

  • One H1 headline

    Your main headline reads: “ULTBIAS US”.

  • Canonical URL set

    The canonical URL is https://ultbias.us/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://ultbias.us/sitemap.xml.

AI search readiness

100
4 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: 5 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (603 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://ultbias.us/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 2 linked pages hidden from search

    https://ultbias.us/customer_authentication/redirect and https://ultbias.us/pages/subscribe-to-be-notified are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 11 pages without a meta description

    https://ultbias.us/customer_authentication/redirect, https://ultbias.us/pages/subscribe-to-be-notified, https://ultbias.us/pages/rewards-program-page, https://ultbias.us/pages/bt21-minini-hero-page, https://ultbias.us/collections/new-arrivals and https://ultbias.us/collections/a4-mycollection-binders and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://ultbias.us/customer_authentication/redirect, https://ultbias.us/pages/subscribe-to-be-notified, https://ultbias.us/pages/contact, https://ultbias.us/pages/bt21-minini-hero-page and https://ultbias.us/pages/ultbias-with-bt21-magic-recipe have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://ultbias.us/customer_authentication/redirect, https://ultbias.us/collections/new-arrivals, https://ultbias.us/collections/a4-mycollection-binders, https://ultbias.us/collections/a4-pages, https://ultbias.us/collections/all-a5-binders and https://ultbias.us/collections/all-custom-a5-pocket-pages and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

Best practices

2 to fixGoogle 9687
  • 21 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were 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

2 to fix75
  • 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 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 507 words of copy

    The homepage carries about 507 words of visible text.

  • Urgency cues

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

4 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop”, “Pre-Order” and “Contact”.

  • 10 short forms

    10 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 cookies, 2 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.

  • 49 other companies contacted

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

Apps on your store

Your storefront loads 25 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geo Pro Geolocation · Eg Auto Add To Cart · Swish · Tinyseo Ai Seo Speed · Microsoft Clarity · Minmaxify Order Limits · Password Lock Pages · Klaviyo Email Marketing Sms · Cartbot · Easylocation · Aftersell · Selleasy · Cartbite · Moast · Easify Box Builder · powr.io · route.com · loox.io · rise-ai.com · gorgias.chat · nfcube.com · 9gtb.com · instant.one · base44.app · Hulk Product Options

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on prismplatinum.us, including 18 speed issues, 2 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