tossit.game website review

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

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

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

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

5 third-party services load with your homepage (Klaviyo, ultimsuite.com and Shopify and others), adding 346 KiB and 386 ms of main-thread time.

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

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

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

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

24 KiB could be saved by minifying JavaScript.

1 image could be 16 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB JavaScript is shipped twice across bundles.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Friends and family playing Tossit, sticking darts to the wa…”.

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

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

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

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

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

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

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

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

Your homepage downloads 8.6 MB in 197 requests on a phone: media 6.8 MB (1), other files 593 KiB (55) and scripts 552 KiB (82). Under 2 MB keeps phones on slow connections fast.

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

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

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

Elements with visible text labels do not have matching accessible names. (11 elements).

Your title is 70 characters, so Google will cut it off around 60: “TOSSIT. Most advanced silicone darts for greater fun. Everywhere anyti”.

There are 2 <h1> headlines (“” and “Darts, No Holes.”). One clear main headline is easier for people and search engines.

Your meta description is 315 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 77 pages on tossit.game and 16 external pages.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://tossit.game/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://tossit.game/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://tossit.game/en-us and https://tossit.game/products/eu-tossit-game-original-starter-pack all use the title “TOSSIT. Most advanced silicone darts for greater fun. Everywhere anyti”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://tossit.game/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://tossit.game/en-us/collections/starter-pack, https://tossit.game/en-us/collections/all, https://tossit.game/collections/all, https://tossit.game/en-us/collections/night-lamps and https://tossit.game/en-us/blogs/news use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://tossit.game/collections/all, whose canonical is https://tossit.game/en-us/collections/all. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://tossit.game/en-us/pages/halloween and https://tossit.game/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

https://tossit.game/customer_authentication/redirect took over 3 s to send its HTML from our server.

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

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Before a visitor clicks anything, the page loads Klaviyo 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.

Opening the homepage sets 9 cookies (measured from a US location before any click).

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.

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