Website review, no card needed

tobioskits.com logo

tobioskits.com website review

Visit site (opens in a new tab)Reviewed 6 November 202624 issues · 86 checks

This review found 24 issues worth fixing on tobioskits.com, 7 of them high impact, across 86 checks. The most urgent: render-blocking requests. 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.1 s1.7 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20262.0 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.9 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
183 ms140 msMay 16Oct 31178 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026160 ms
May 23, 2026162 ms
May 30, 2026162 ms
Jun 6, 2026163 ms
Jun 13, 2026162 ms
Jun 20, 2026154 ms
Jun 27, 2026152 ms
Jul 4, 2026149 ms
Jul 11, 2026145 ms
Jul 18, 2026146 ms
Jul 25, 2026150 ms
Aug 1, 2026153 ms
Aug 8, 2026155 ms
Aug 15, 2026158 ms
Aug 22, 2026155 ms
Aug 29, 2026160 ms
Sep 5, 2026162 ms
Sep 12, 2026166 ms
Sep 19, 2026171 ms
Sep 26, 2026172 ms
Oct 3, 2026175 ms
Oct 10, 2026175 ms
Oct 17, 2026176 ms
Oct 24, 2026176 ms
Oct 31, 2026178 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 tobioskits.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tobioskits.com at 0.6 s0.6 s
  2. tobioskits.com at 1.2 s1.2 s
  3. tobioskits.com at 1.8 s1.8 s
  4. tobioskits.com at 2.3 s2.3 s
  5. tobioskits.com at 2.9 s2.9 s
  6. tobioskits.com at 3.5 s3.5 s
  7. tobioskits.com at 4.1 s4.1 s
  8. tobioskits.com at 4.7 s4.7 s

Speed

5 to fix81
  • Render-blocking requests

    1.4 s

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

  • 5,722 HTML elements

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

  • Mobile performance score: 81

    81/100

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

  • Reduce unused JavaScript

    300 ms · 600 KiB

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

  • Reduce unused CSS

    300 ms · 79 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, omnisnippet1.com and shrinetheme.com and others), adding 461 KiB and 337 ms of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 127 KiB

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

  • 2 long tasks on the main thread

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

  • Improve image delivery

    44 KiB

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

  • Minify JavaScript

    21 KiB

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

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 15 ms

    15 ms

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

Core Web Vitals

7 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: 4.4 s

    4.4 s

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

  • Real-user INP: 205 ms

    205 ms

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

  • Real-user TTFB: 925 ms

    925 ms

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • Time to Interactive: 5.3 s

    5.3 s

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

  • 2 images without width and height

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

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

    +10%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 160 ms to 178 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-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

    Real visitors wait 1.9 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: 1.7 s

    1.7 s

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

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 13 ms

    13 ms

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

Images and page weight

100
  • 1 image in older formats

    1 image (73 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.

  • About 0.3 g of CO₂ per visit

    0.29 g

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

3 checks passed
  • Page weight: 1.0 MB in 119 requests

    1.0 MB

    Your homepage downloads 1.0 MB in 119 requests on a phone: scripts 555 KiB (69), HTML 161 KiB (2) and images 137 KiB (12). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9294
  • 36 text elements with low contrast

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

  • 3 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (6 elements)

    ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

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

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

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

Google 92100
  • 226 internal links, 19 external

    The homepage links to 226 pages on tobioskits.com and 19 external pages.

8 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Shop Tobios Kits for portable watercolor, embroidery & art kits. Everything you need in one box to relax and create. 60…”.

  • One H1 headline

    Your main headline reads: “VIP BLACK FRIDAY SALE”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Tobios Kits | Official Store for Watercolor & Embroidery Kits”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Brand, Organization, WebPage 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://tobioskits.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://tobioskits.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 description; contact details would complete it.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 6 pages without an H1

    https://tobioskits.com/pages/accessibility-statement, https://tobioskits.com/collections/watercolor-kits, https://tobioskits.com/collections/tobios-workbooks, https://tobioskits.com/collections/watercolor-paints, https://tobioskits.com/collections/watercolor-brushes and https://tobioskits.com/collections/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 80 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 6 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 6 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9271
  • 1 broken image

    1 image failed to load on a phone, for example https://tobioskits.com/.

  • 5 small tap targets

    5 of 20 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: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix83
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 1,770 words of copy

    The homepage carries about 1,770 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Best Sellers”.

  • 24 calls to action

    The homepage has 24 calls to action, for example “SHOP CLEARANCE”, “SHOP ALL” and “Contact Us”.

  • 7 short forms

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

  • Social proof on the page

    Social proof on the homepage: 74 testimonial or review blocks, a star rating, 2 trust badges and “200,00+ customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager, PostHog and TikTok Pixel.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 11 cookies set on arrival

    11

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

  • 14 other companies contacted

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

Apps your storefront loads

Sitemap Noindex Pro Seo · Aimerce First Party Pixel · Judge Me Reviews · Elevate Ab Testing · Ez Product Translate · Applovin Shop Integration · Omnisend · Pixiehog · Discount Mixer · goaffpro.com · bestads.com · richpanel.com · cloudfront.net · amazonaws.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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | PostHog
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on tobioskits.com, including 12 speed 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