Website review, no card needed

figsscrubs.com logo

figsscrubs.com website review

Visit site (opens in a new tab)Reviewed 6 November 202638 issues · 76 checks

This review found 38 issues worth fixing on figsscrubs.com, 14 of them high impact, across 76 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

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

How it loaded on a phone

  1. figsscrubs.com at 1.2 s1.2 s
  2. figsscrubs.com at 2.5 s2.5 s
  3. figsscrubs.com at 3.7 s3.7 s
  4. figsscrubs.com at 5.0 s5.0 s
  5. figsscrubs.com at 6.2 s6.2 s
  6. figsscrubs.com at 7.4 s7.4 s
  7. figsscrubs.com at 8.7 s8.7 s
  8. figsscrubs.com at 9.9 s9.9 s

Speed

12 to fix35
  • Reduce unused JavaScript

    3.8 s · 2.6 MB

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

  • Google Tag Manager adds 3.0 s

    3.0 s

    Google Tag Manager costs a phone 3.0 s of main-thread work and 3.2 MB 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: 11.6 s

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

  • Mobile performance score: 35

    35/100

    Your mobile performance score is 35. 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 (Google Tag Manager, fbot.me and Facebook and others), adding 9.7 MB and 4.0 s of main-thread time.

  • Use efficient cache lifetimes

    250 ms · 2.0 MB

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

  • Avoid multiple page redirects

    901 ms

    The page goes through 1 redirect before it starts loading, costing about 901 ms. Link and advertise the final URL directly.

  • Vimeo adds 75 ms

    75 ms

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

  • 20 long tasks on the main thread

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

  • Improve image delivery

    382 KiB

    1 image could be 382 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • fbot.me adds 294 ms

    294 ms

    fbot.me costs a phone 294 ms of main-thread work and 748 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.

  • 2,230 HTML elements

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

  • Legacy JavaScript

    122 KiB

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

  • Duplicated JavaScript

    98 KiB

    98 KiB JavaScript is shipped twice across bundles.

  • Reduce unused CSS

    45 KiB

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

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 27 ms

    27 ms

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

Core Web Vitals

8 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: 18.2 s

    18.2 s

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

  • Speed Index: 19.8 s

    19.8 s

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

  • Time to Interactive: 65.5 s

    65.5 s

    The page becomes fully interactive after 65.5 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.

  • Real-user INP: 316 ms

    316 ms

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • 8 images without width and height

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

5 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.045

    0.045

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

Images and page weight

2 to fix64
  • Page weight: 14.5 MB in 606 requests

    14.5 MB

    Your homepage downloads 14.5 MB in 606 requests on a phone: scripts 7.5 MB (172), other files 5.1 MB (284) and images 1.2 MB (112). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    NEVER_CHANGE_HOLIDAY_WHITE.png 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 4.1 g of CO₂ per visit

    4.11 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.11 g of CO₂e: 492.8 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

4 to fixGoogle 10094
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Positive tabindex

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

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

5 to fixGoogle 9269
  • Page is set to noindex

    The robots meta tag says “noindex, nofollow, noarchive”: Google is told not to list this page at all.

  • Canonical points to another host

    Your canonical URL points to wearfigs.com, not shop.wearfigs.com, so Google may credit that host instead.

  • No structured data

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

  • Only 1 internal link

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

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

6 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Shop FIGS for comfortable designer scrubs and medical apparel that’s 100% awesome. Tons of colors and fashionable style…”.

  • One H1 headline

    Your main headline reads: “WHY WEAR SCRUBS WHEN YOU CAN #WEARFIGS”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “FIGS - Premium Scrubs, Medical Uniforms & Apparel”.

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

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    45%

    The HTML your server sends has 152 of the 336 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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.

  • llms.txt published

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

Best practices

3 to fixGoogle 7385
  • 48 small tap targets

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

  • 3 third-party cookies

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “jQuery is not defined”.

  • Missing source maps

    Large scripts ship without source maps.

  • 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

2 to fix70
  • 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.

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

  • About 336 words of copy

    The homepage carries about 336 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP WOMEN” and “SHOP MEN”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Sign up for texts” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 15 cookies set on arrival

    15

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

  • 10 other companies contacted

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

2 checks passed
  • Consent tool: OneTrust

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

  • 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 figsscrubs.com, 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 18 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Friendbuy Loyalty Referrals · privy.com · wearfigs.com · cloudfront.net · integrations-itbl.co · fbot.me · global-e.com · snapchat.com · pepperjam.com · attn.tv · nosto.com · trustpilot.com · creditsyard.com · botnot.io · signifyd.com · hubapi.com · siena.cx · rise-ai.com

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

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on figsscrubs.com, including 20 speed issues, 5 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