Website review, no card needed

g59recordsmerchandise.com logo

g59recordsmerchandise.com website review

Visit site (opens in a new tab)Reviewed 16 November 202639 issues · 83 checks

This review found 39 issues worth fixing on g59recordsmerchandise.com, 15 of them high impact, across 83 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.3 s1.6 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.2 s
Jun 6, 20261.9 s
Jun 13, 20261.8 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20262.1 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.7 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Oct 24, 20261.8 s
Oct 31, 20261.9 s
Nov 7, 20261.9 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
191 ms136 msMay 30Nov 14163 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026161 ms
Jun 6, 2026161 ms
Jun 13, 2026164 ms
Jun 20, 2026161 ms
Jun 27, 2026163 ms
Jul 4, 2026172 ms
Jul 11, 2026178 ms
Jul 25, 2026154 ms
Aug 1, 2026160 ms
Aug 8, 2026159 ms
Aug 15, 2026155 ms
Aug 22, 2026185 ms
Aug 29, 2026155 ms
Sep 5, 2026155 ms
Sep 12, 2026152 ms
Sep 19, 2026144 ms
Sep 26, 2026146 ms
Oct 3, 2026142 ms
Oct 10, 2026146 ms
Oct 17, 2026151 ms
Oct 24, 2026160 ms
Oct 31, 2026167 ms
Nov 7, 2026172 ms
Nov 14, 2026163 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 g59recordsmerchandise.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. g59recordsmerchandise.com at 0.9 s0.9 s
  2. g59recordsmerchandise.com at 1.8 s1.8 s
  3. g59recordsmerchandise.com at 2.7 s2.7 s
  4. g59recordsmerchandise.com at 3.6 s3.6 s
  5. g59recordsmerchandise.com at 4.5 s4.5 s
  6. g59recordsmerchandise.com at 5.4 s5.4 s
  7. g59recordsmerchandise.com at 6.3 s6.3 s
  8. g59recordsmerchandise.com at 7.2 s7.2 s

Speed

12 to fix39
  • Use efficient cache lifetimes

    8.5 s · 5.9 MB

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

  • Improve image delivery

    6.0 s · 5.3 MB

    36 images could be 5.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.0 s faster on a phone.

  • Reduce unused JavaScript

    3.3 s · 605 KiB

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

  • Avoid multiple page redirects

    2.4 s

    The page goes through 2 redirects before it starts loading, costing about 2.4 s. Link and advertise the final URL directly.

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, g59records.com and Facebook and others), adding 7.6 MB and 1.4 s of main-thread time.

  • g59records.com adds 328 ms

    328 ms

    g59records.com costs a phone 328 ms of main-thread work and 6.0 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.

  • Google Tag Manager adds 606 ms

    606 ms

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

  • Legacy JavaScript

    450 ms · 72 KiB

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

  • Main-thread work: 3.0 s

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

  • Facebook adds 220 ms

    220 ms

    Facebook costs a phone 220 ms of main-thread work and 304 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.

  • Klaviyo adds 114 ms

    114 ms

    Klaviyo costs a phone 114 ms of main-thread work and 313 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.

  • 11 long tasks on the main thread

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

  • Document request latency

    200 ms

    The HTML itself could arrive about 200 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • Font display

    50 ms

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

  • 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: 3 ms

    3 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 53.2 s

    53.2 s

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

  • Time to Interactive: 55.7 s

    55.7 s

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

  • Speed Index: 10.5 s

    10.5 s

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

  • Total Blocking Time: 737 ms

    737 ms

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Cumulative Layout Shift: 0.122

    0.122

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

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

    1.8 s

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

  • Real-user INP: 166 ms

    166 ms

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

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (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: 707 ms

    707 ms

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

Images and page weight

5 to fix14
  • Page weight: 20.2 MB in 231 requests

    20.2 MB

    Your homepage downloads 20.2 MB in 231 requests on a phone: images 18.0 MB (69), scripts 1.9 MB (83) and fonts 155 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.

  • 7 images far larger than shown

    2.4 MB

    7 images are downloaded at several times the size a phone draws them, for example image at 1,536 px wide, shown at 176 px. Resized copies would save about 2.4 MB.

  • 26 images in older formats

    26 images (4.4 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.

  • An image on the first screen is lazy-loaded

    image 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 5.7 g of CO₂ per visit

    5.74 g

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

Accessibility

4 to fixGoogle 9092
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • All page content should be contained by landmarks (41 elements)

    All page content should be contained by landmarks: 41 elements on the page fail this check, rated moderate by axe-core.

  • 88 form fields without a label

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

  • 1 link without text

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

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 27 automated accessibility rules passed

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

SEO

4 to fixGoogle 10081
  • No H1 headline

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

  • Meta description is short (69 characters)

    Your meta description is only 69 characters: “Death is nothing but a promise. At least look the part. GREYFIVENINE.”. 70 to 160 characters is enough to sell the click.

  • No social preview image

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 40 internal links, 7 external

    The homepage links to 40 pages on g59recordsmerchandise.com and 7 external pages.

5 checks passed
  • Title: 40 characters

    Your title is a healthy 40 characters: “GREYFIVENINE – g59recordsmerchandise.com”.

  • Canonical URL set

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

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

AI search readiness

2 to fix75
  • Some text only appears after JavaScript runs

    57%

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

  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, 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.

  • No llms.txt

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

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

Other pages

1 to fix95
  • 5 pages without a meta description

    https://www.g59recordsmerchandise.com/collections/all, https://www.g59recordsmerchandise.com/collections/grey-friday-1, https://www.g59recordsmerchandise.com/collections/new-arrivals, https://www.g59recordsmerchandise.com/collections/tops and https://www.g59recordsmerchandise.com/collections/tees have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9691
  • 43 distorted images

    43 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

    The homepage carries about 255 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop” and “look book”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “SHOP”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

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.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 cookies, 6 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.

  • 24 other companies contacted

    Loading the homepage contacts 24 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 g59recordsmerchandise.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 39 issues on g59recordsmerchandise.com, including 18 speed issues, 4 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