Website review, no card needed

sketchfab.com logo

sketchfab.com website review

Visit site (opens in a new tab)Reviewed 11 October 202631 issues · 71 checks

This review found 31 issues worth fixing on sketchfab.com, 12 of them high impact, across 71 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

Real-visitor load time (LCP)75th percentile, phones
2.3 s1.9 sApr 18Oct 32.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20262.1 s
Apr 25, 20262.1 s
May 2, 20262.1 s
May 9, 20262.1 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.1 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20262.0 s
Sep 26, 20262.2 s
Oct 3, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
336 ms294 msApr 18Oct 3300 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026325 ms
Apr 25, 2026326 ms
May 2, 2026330 ms
May 9, 2026331 ms
May 16, 2026330 ms
May 23, 2026327 ms
May 30, 2026320 ms
Jun 6, 2026318 ms
Jun 13, 2026316 ms
Jun 20, 2026316 ms
Jun 27, 2026317 ms
Jul 4, 2026315 ms
Jul 11, 2026313 ms
Jul 18, 2026311 ms
Jul 25, 2026311 ms
Aug 1, 2026311 ms
Aug 8, 2026309 ms
Aug 15, 2026310 ms
Aug 22, 2026308 ms
Aug 29, 2026305 ms
Sep 5, 2026305 ms
Sep 12, 2026302 ms
Sep 19, 2026300 ms
Sep 26, 2026299 ms
Oct 3, 2026300 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 sketchfab.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sketchfab.com at 1.5 s1.5 s
  2. sketchfab.com at 3.1 s3.1 s
  3. sketchfab.com at 4.6 s4.6 s
  4. sketchfab.com at 6.1 s6.1 s
  5. sketchfab.com at 7.7 s7.7 s
  6. sketchfab.com at 9.2 s9.2 s
  7. sketchfab.com at 10.7 s10.7 s
  8. sketchfab.com at 12.3 s12.3 s

Speed

5 to fix39
  • Reduce unused JavaScript

    5.0 s · 876 KiB

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

  • Mobile performance score: 39

    39/100

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

  • Render-blocking requests

    450 ms

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

  • Reduce unused CSS

    300 ms · 108 KiB

    About 108 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.

  • 3 long tasks on the main thread

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

  • Use efficient cache lifetimes

    200 ms · 41 KiB

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

  • Improve image delivery

    73 KiB

    2 images could be 73 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Optanon and Sentry), adding 141 KiB and 37 ms of main-thread time.

  • Legacy JavaScript

    18 KiB

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

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

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 78 ms

    78 ms

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

Core Web Vitals

12 to fix33
  • 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.

  • Real-user INP: 991 ms

    991 ms

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

  • Largest Contentful Paint: 15.4 s

    15.4 s

    Your largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The leading platform for 3D & AR on the web”.

  • Time to Interactive: 15.4 s

    15.4 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Real-user CLS: 0.11

    0.11

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0.235

    0.235

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

  • Total Blocking Time: 357 ms

    357 ms

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

  • 12 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -8%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

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

Images and page weight

1 to fix67
  • Page weight: 2.5 MB in 117 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 117 requests on a phone: scripts 1.7 MB (63), fonts 394 KiB (10) and images 270 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.71 g

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

Accessibility

4 to fixGoogle 9677
  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 10 text elements with low contrast

    10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 6 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • No XML sitemap

    No XML sitemap at https://sketchfab.com/sitemap.xml, so Google discovers your pages only by following links.

  • 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 set, so this is minor.

  • 72 internal links, 8 external

    The homepage links to 72 pages on sketchfab.com and 8 external pages.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “With a community of over one million creators, we are the world’s largest platform to publish, share, and discover 3D c…”.

  • One H1 headline

    Your main headline reads: “The leading platformfor 3D & AR on the web”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Sketchfab - The best 3D viewer on the web”.

  • Canonical URL set

    The canonical URL is https://sketchfab.com/.

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

AI search readiness

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

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

3 to fix75
  • 12 pages without a title

    https://sketchfab.com/collections/popular, https://sketchfab.com/blogs/community, https://sketchfab.com/members, https://sketchfab.com/masters, https://sketchfab.com/3d-models/categories/animals-pets and https://sketchfab.com/3d-models/categories/architecture and 6 others have no <title>, so Google invents the link text in results.

  • 12 pages without a meta description

    https://sketchfab.com/collections/popular, https://sketchfab.com/blogs/community, https://sketchfab.com/members, https://sketchfab.com/masters, https://sketchfab.com/3d-models/categories/animals-pets and https://sketchfab.com/3d-models/categories/architecture and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://sketchfab.com/collections/popular, https://sketchfab.com/blogs/community, https://sketchfab.com/members, https://sketchfab.com/masters, https://sketchfab.com/3d-models/categories/animals-pets and https://sketchfab.com/3d-models/categories/architecture and 6 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 48 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.

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

Best practices

Google 96100
  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 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 293 words of copy

    The homepage carries about 293 words of visible text.

3 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Pricing”, “Sign Up” and “join for free”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

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

Privacy and tracking

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

  • 1 other company contacted

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

1 checks passed
  • 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 sketchfab.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 31 issues on sketchfab.com, including 17 speed issues, 2 SEO issues and 3 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