Website review, no card needed

wraith.studio logo

wraith.studio website review

Visit site (opens in a new tab)Reviewed 6 November 202632 issues · 79 checks

This review found 32 issues worth fixing on wraith.studio, 10 of them high impact, across 79 checks. The most urgent: 1 button without a name. 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.5 s959 msMay 16Oct 311.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.4 s
Jul 25, 20261.5 s
Aug 1, 20261.3 s
Aug 8, 20261.2 s
Aug 15, 20261.1 s
Aug 22, 20261.0 s
Aug 29, 20261.0 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
134 ms99 msMay 16Oct 24125 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026127 ms
May 23, 2026125 ms
May 30, 2026121 ms
Jun 6, 2026125 ms
Jun 13, 2026127 ms
Jun 20, 2026126 ms
Jun 27, 2026130 ms
Jul 4, 2026130 ms
Jul 11, 2026126 ms
Jul 18, 2026130 ms
Jul 25, 2026127 ms
Aug 1, 2026107 ms
Aug 8, 2026107 ms
Aug 15, 2026115 ms
Aug 22, 2026104 ms
Aug 29, 2026107 ms
Sep 5, 2026107 ms
Sep 12, 2026103 ms
Sep 19, 2026117 ms
Sep 26, 2026115 ms
Oct 3, 2026121 ms
Oct 10, 2026125 ms
Oct 17, 2026128 ms
Oct 24, 2026125 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 wraith.studio (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wraith.studio at 0.7 s0.7 s
  2. wraith.studio at 1.4 s1.4 s
  3. wraith.studio at 2.1 s2.1 s
  4. wraith.studio at 2.8 s2.8 s
  5. wraith.studio at 3.6 s3.6 s
  6. wraith.studio at 4.3 s4.3 s
  7. wraith.studio at 5.0 s5.0 s
  8. wraith.studio at 5.7 s5.7 s

Speed

6 to fix69
  • Improve image delivery

    950 ms · 391 KiB

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

  • Mobile performance score: 69

    69/100

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

  • Use efficient cache lifetimes

    800 ms · 101 KiB

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

  • Render-blocking requests

    550 ms

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

  • Reduce unused JavaScript

    330 ms · 70 KiB

    About 70 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 330 ms faster on a phone.

  • Main-thread work: 2.1 s

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

  • Legacy JavaScript

    200 ms · 16 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Shopify, loox.io and Lucky Orange and others), adding 189 KiB and 72 ms of main-thread time.

  • Reduce unused CSS

    30 ms · 10 KiB

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

  • Minify JavaScript

    10 ms · 4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    7 KiB

    7 KiB JavaScript is shipped twice across bundles.

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

    4 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 9.0 s

    9.0 s

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

  • Time to Interactive: 9.1 s

    9.1 s

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

  • Speed Index: 5.5 s

    5.5 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

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

    1.1 s

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

  • 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: 0.7 s

    0.7 s

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

  • Real-user TTFB: 435 ms

    435 ms

    Real visitors wait 435 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).

  • 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

2 to fix75
  • Page weight: 2.2 MB in 204 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 204 requests on a phone: images 814 KiB (44), other files 759 KiB (92) and scripts 407 KiB (42). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    47 KiB

    1 image is downloaded at several times the size a phone draws it, for example space-travel-cover_2cc6e6aa-fd32-4ad9-ac82-aa60862abde5.png at 1,250 px wide, shown at 175 px. Resized copies would save about 47 KiB.

  • 2 images below the first screen load straight away

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

  • About 0.6 g of CO₂ per visit

    0.63 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

6 to fixGoogle 8589
  • 1 button without a name

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

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

  • Summary elements must have discernible text (1 element)

    Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

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

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

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

  • Headings skip levels

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

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 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 9291
  • Title is short (13 characters)

    Your title is only 13 characters: “Wraith Studio”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No favicon declared

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

  • 115 internal links, 3 external

    The homepage links to 115 pages on wraith.studio and 3 external pages.

7 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Transform Your Workspace with Wraith Studio: Explore a wide range of organization, productivity, and workspace accessor…”.

  • One H1 headline

    Your main headline reads: “Rombica mysound Jazz”.

  • Canonical URL set

    The canonical URL is https://wraith.studio/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://wraith.studio/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 (549 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix76
  • 3 pages point its canonical at the homepage

    /products/wraith-studio-monitor-kolu, /products/wraith-studio-kablo-organizatoru and /products/scents-of-myths-x-wraith-studio-soya-mumu declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 4 pages share a title

    /, /products/wraith-studio-monitor-kolu, /products/wraith-studio-kablo-organizatoru and /products/scents-of-myths-x-wraith-studio-soya-mumu all use the title “Wraith Studio”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    /collections/klavyeler, /collections/usb-hub, /collections/mouselar, /collections/deskmats, /collections/standlar and /collections/seramikler and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    /products/wraith-studio-monitor-kolu, /products/wraith-studio-kablo-organizatoru and /products/scents-of-myths-x-wraith-studio-soya-mumu use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 15 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 8 distorted images

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 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.

  • 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 456 words of copy

    The homepage carries about 456 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Türkiye (TRY ₺)” and “Japonya (TRY ₺)”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 10 cookies set on arrival

    10

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

  • 21 other companies contacted

    Loading the homepage contacts 21 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 wraith.studio, 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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Gdpr Production · luckyorange.com · loox.io

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on wraith.studio, including 10 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