Website review, no card needed

lastresortab.com logo

lastresortab.com website review

Visit site (opens in a new tab)Reviewed 12 November 202627 issues · 76 checks

This review found 27 issues worth fixing on lastresortab.com, 7 of them high impact, across 76 checks. The most urgent: hidden but focusable. 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.2 s961 msMay 23Nov 71.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.0 s
May 30, 20261.0 s
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.0 s
Oct 10, 2026988 ms
Oct 17, 20261.0 s
Oct 24, 20261.0 s
Oct 31, 20261.0 s
Nov 7, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
132 ms100 msMay 23Nov 7124 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026112 ms
May 30, 2026111 ms
Jun 6, 2026106 ms
Jun 13, 2026106 ms
Jun 20, 2026104 ms
Jun 27, 2026104 ms
Jul 4, 2026108 ms
Jul 11, 2026112 ms
Jul 18, 2026114 ms
Jul 25, 2026124 ms
Aug 1, 2026127 ms
Aug 8, 2026127 ms
Aug 15, 2026128 ms
Aug 22, 2026117 ms
Aug 29, 2026110 ms
Sep 5, 2026107 ms
Sep 12, 2026109 ms
Sep 19, 2026109 ms
Sep 26, 2026111 ms
Oct 3, 2026110 ms
Oct 10, 2026108 ms
Oct 17, 2026109 ms
Oct 24, 2026114 ms
Oct 31, 2026122 ms
Nov 7, 2026124 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 lastresortab.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lastresortab.com at 0.8 s0.8 s
  2. lastresortab.com at 1.7 s1.7 s
  3. lastresortab.com at 2.5 s2.5 s
  4. lastresortab.com at 3.4 s3.4 s
  5. lastresortab.com at 4.2 s4.2 s
  6. lastresortab.com at 5.1 s5.1 s
  7. lastresortab.com at 5.9 s5.9 s
  8. lastresortab.com at 6.7 s6.7 s

Speed

6 to fix73
  • Mobile performance score: 73

    73/100

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

  • Render-blocking requests

    750 ms

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

  • Improve image delivery

    300 ms · 371 KiB

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

  • Reduce unused CSS

    300 ms · 56 KiB

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

  • 1,870 HTML elements

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

  • Shopify adds 90 ms

    90 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Klaviyo and b-cdn.net and others), adding 687 KiB and 196 ms of main-thread time.

  • Reduce unused JavaScript

    28 KiB

    About 28 KiB of JavaScript is downloaded but never used on this page.

  • Legacy JavaScript

    19 KiB

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

  • Use efficient cache lifetimes

    14 KiB

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

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

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 584 ms of it running JavaScript. That is comfortably low.

  • Server response: 81 ms

    81 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 7.7 s

    7.7 s

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

  • Time to Interactive: 7.9 s

    7.9 s

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

  • Speed Index: 4.6 s

    4.6 s

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

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

    +10%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user INP: 113 ms

    113 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 509 ms

    509 ms

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

  • First Contentful Paint: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix60
  • 1 image over 500 KB

    C_I_16x9_2ba604d1-13cc-4497-a872-f7c496d0f62b.gif weighs 849 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.8 MB in 422 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 422 requests on a phone: images 1.6 MB (31), other files 1.1 MB (200) and scripts 784 KiB (171). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (849 KiB) is 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.

  • 5 images below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.09 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.09 g of CO₂e: 130.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 8693
  • Hidden but focusable

    16 elements hidden from screen readers can still receive keyboard focus.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 2 images without alt text

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

  • 15 links without text

    15 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 9288
  • Title is short (14 characters)

    Your title is only 14 characters: “Last Resort AB”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (24 characters)

    Your meta description is only 24 characters: “Here to expand your mind”. 70 to 160 characters is enough to sell the click.

  • 81 internal links, 4 external

    The homepage links to 81 pages on lastresortab.com and 4 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Last Resort AB”.

  • Canonical URL set

    The canonical URL is https://www.lastresortab.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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://www.lastresortab.com/sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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://www.lastresortab.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix88
  • 7 pages without a meta description

    https://www.lastresortab.com/collections/shoes, https://www.lastresortab.com/collections/apparel, https://www.lastresortab.com/collections/accessories, https://www.lastresortab.com/collections/early-access-summer-sale-2026, https://www.lastresortab.com/blogs/news and https://www.lastresortab.com/pages/team and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.lastresortab.com/products/vm001-suede-lo-old-blue-white, https://www.lastresortab.com/products/vm001-lo-suede-old-red-white and https://www.lastresortab.com/products/vm001-suede-lo-white-white use the same meta description. A description written for each page earns more clicks.

  • 13 pages without an H1

    https://www.lastresortab.com/collections/frontpage, https://www.lastresortab.com/collections/shoes, https://www.lastresortab.com/collections/apparel, https://www.lastresortab.com/collections/accessories, https://www.lastresortab.com/collections/early-access-summer-sale-2026 and https://www.lastresortab.com/blogs/news and 7 others have 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 42 found) and read each the way a search engine does.

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

  • 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

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    37 of 40 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 130 words

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

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

3 checks passed
  • Clear next step on the first screen

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

  • 10 calls to action

    The homepage has 10 calls to action, for example “US SHOP”, “Shop” and “Archive Shop”.

  • 4 short forms

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

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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 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.

  • 27 other companies contacted

    Loading the homepage contacts 27 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 lastresortab.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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Depict Search Merchandising · Klaviyo Email Marketing Sms · herokuapp.com · b-cdn.net · nfcube.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

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Stockholm

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on lastresortab.com, including 9 speed issues, 2 SEO issues and 4 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