trycreate.co website review

15 images could be 622 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

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

8 third-party services load with your homepage (alia-prod.com, Shopify and rebuyengine.com and others), adding 2.1 MB and 1.8 s of main-thread time.

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

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

alia-prod.com costs a phone 534 ms of main-thread work and 672 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.

Shopify costs a phone 529 ms of main-thread work and 659 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.

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

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

rebuyengine.com costs a phone 207 ms of main-thread work and 400 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.

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

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 10.8 MB in 485 requests on a phone: images 6.8 MB (120), scripts 2.1 MB (156) and other files 876 KiB (160). Under 2 MB keeps phones on slow connections fast.

10 images are downloaded at several times the size a phone draws them, for example Darren_Candow_Headshot.jpg at 390 px wide, shown at 60 px. Resized copies would save about 994 KiB.

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

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

<svg> elements with an img or image role must have alternative text: 112 elements on the page fail this check, rated serious by axe-core.

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

14 tap targets are too small or too close together to hit reliably with a finger.

Some lists contain elements other than list items, which screen readers announce wrongly.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

22 visible links have no text or label, so screen readers cannot say where they go.

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

Your title is only 22 characters: “Creatine for Everybody”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 5 <h1> headlines (“Daily Creatine.With a sour twist.”, “Daily Creatine.With a sour twist.” and “Two electric flavors.Double the gains.”). One clear main headline is easier for people and search engines.

There is no robots.txt at trycreate.co/robots.txt, the first file search crawlers ask for.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 110 pages on trycreate.co and 5 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

/discount/SOURSUMMER, /discount/LEMONADE, /discount/JUICEBOX and /discount/LFGUMMY 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.

/, /discount/SOURSUMMER, /discount/LEMONADE, /discount/JUICEBOX and /discount/LFGUMMY all use the title “Creatine for Everybody”. Search engines can't tell which page to show for a search, so each competes with the others.

/products/creatine-monohydrate-stick-packs, /pages/the-science, /pages/our-quality-promise, /pages/create-referral-program and /products/creatine-electrolytes-mix-variety-bundles have no meta description, so Google writes the search snippet from whatever text it finds.

/discount/SOURSUMMER, /discount/LEMONADE, /discount/JUICEBOX and /discount/LFGUMMY use the same meta description. A description written for each page earns more clicks.

/products/creatine-electrolytes-mix, /products/creatine-monohydrate-gummies, /products/create-bundles, /pages/create-referral-program, /products/creatine-electrolytes-mix-variety-bundles and /pages/creatine-monohydrate-products-all have no <h1> headline, so visitors and search engines get no clear main topic.

/products/creatine-electrolytes-mix and /products/create-bundles have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/discount/LFGUMMY took over 3 s to send its HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

Chrome logged issues while loading the page (“Cookie”).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

trycreate.co has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

The homepage carries about 3,452 words of visible text.

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

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Amazon Ads, Google Tag Manager, Klaviyo, Microsoft Clarity and Snap 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 54 cookies, 2 of them by other companies (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 64 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.