Website review, no card needed

johnnywas.com logo

johnnywas.com website review

Visit site (opens in a new tab)Reviewed 30 October 202641 issues · 90 checks

This review found 41 issues worth fixing on johnnywas.com, 17 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. 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.5 s2.1 sMay 9Oct 242.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.3 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.3 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
234 ms192 msMay 9Oct 24229 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026197 ms
May 16, 2026198 ms
May 23, 2026198 ms
May 30, 2026205 ms
Jun 6, 2026212 ms
Jun 13, 2026213 ms
Jun 20, 2026210 ms
Jun 27, 2026209 ms
Jul 4, 2026213 ms
Jul 11, 2026213 ms
Jul 18, 2026220 ms
Jul 25, 2026217 ms
Aug 1, 2026210 ms
Aug 8, 2026207 ms
Aug 15, 2026209 ms
Aug 22, 2026212 ms
Aug 29, 2026219 ms
Sep 5, 2026214 ms
Sep 12, 2026213 ms
Sep 19, 2026213 ms
Sep 26, 2026213 ms
Oct 3, 2026219 ms
Oct 10, 2026221 ms
Oct 17, 2026228 ms
Oct 24, 2026229 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 johnnywas.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. johnnywas.com at 0.8 s0.8 s
  2. johnnywas.com at 1.5 s1.5 s
  3. johnnywas.com at 2.3 s2.3 s
  4. johnnywas.com at 3.1 s3.1 s
  5. johnnywas.com at 3.9 s3.9 s
  6. johnnywas.com at 4.6 s4.6 s
  7. johnnywas.com at 5.4 s5.4 s
  8. johnnywas.com at 6.2 s6.2 s

Speed

13 to fix39
  • Use efficient cache lifetimes

    6.5 s · 4.8 MB

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

  • Reduce unused JavaScript

    3.4 s · 705 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Duplicated JavaScript

    1.2 s · 102 KiB

    102 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 39

    39/100

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

  • Main-thread work: 5.3 s

    A phone's processor spends 5.3 s on main-thread work while loading, 3.4 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 (Google Tag Manager, Listrak and Facebook and others), adding 1.4 MB and 1.4 s of main-thread time.

  • Improve image delivery

    400 ms · 900 KiB

    6 images could be 900 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • Legacy JavaScript

    750 ms · 75 KiB

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

  • Google Tag Manager adds 577 ms

    577 ms

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

  • Reduce unused CSS

    450 ms · 125 KiB

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

  • Listrak adds 255 ms

    255 ms

    Listrak costs a phone 255 ms of main-thread work and 339 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,660 HTML elements

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

  • 20 long tasks on the main thread

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

  • Font display

    150 ms

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

  • Minify JavaScript

    20 KiB

    20 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: 43 ms

    43 ms

    Your server sent the HTML in 43 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: 28.6 s

    28.6 s

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

  • Time to Interactive: 30.7 s

    30.7 s

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

  • Speed Index: 13.5 s

    13.5 s

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

  • Total Blocking Time: 1.0 s

    1.0 s

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

  • Real-user INP: 216 ms

    216 ms

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

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 9 images without width and height

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

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

    +16%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

3 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user CLS: 0.09

    0.09

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix38
  • Page weight: 10.1 MB in 168 requests

    10.1 MB

    Your homepage downloads 10.1 MB in 168 requests on a phone: media 4.9 MB (2), scripts 2.1 MB (60) and images 1.5 MB (27). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    1015_Hp1_ComponentA_mob.gif weighs 822 KiB. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

    2 images (859 KiB) 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.

  • 3 images below the first screen load straight away

    3 images further down the page (948 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.9 g of CO₂ per visit

    2.87 g

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

1 checks passed
  • 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 9395
  • ARIA toggle fields must have an accessible name (7 elements)

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

  • Inline text spacing must be adjustable with custom stylesheets (3 elements)

    Inline text spacing must be adjustable with custom stylesheets: 3 elements on the page fail this check, rated serious by axe-core.

  • 1 link without text

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

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 67 images in the HTML carry an alt attribute.

  • 50 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: 50 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8389
  • No canonical URL

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

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow 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.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 212 internal links, 3 external

    The homepage links to 212 pages on johnnywas.com and 3 external pages.

6 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “The official Johnny Was website has the best selection of chic clothing, from women's dresses to accessories made with …”.

  • One H1 headline

    Your main headline reads: “DESIGNER & CHIC WOMEN'S CLOTHING”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Johnny Was | Chic Clothing & Vintage-Inspired Style”.

  • Structured data in place

    Structured data found: Organization.

  • 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://www.johnnywas.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.johnnywas.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.

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

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 1 page without an H1

    https://www.johnnywas.com/catalog-request has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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 9270
  • 6 broken images

    6 images failed to load on a phone, for example https://www.johnnywas.com/null.

  • 7 small tap targets

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

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 358 words of copy

    The homepage carries about 358 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request a Catalog”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “Shop Our New Arrivals”, “Request a Catalog” and “Shop New Arrivals”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

  • 8 trackers load before any consent

    8

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

  • 46 cookies set on arrival

    46

    Opening the homepage sets 46 cookies, 1 of them by other companies (measured from a US location before any click).

  • 53 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Akamai

Company

Headquarters
Los Angeles

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on johnnywas.com, including 23 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