Website review, no card needed

kaysalove.com logo

kaysalove.com website review

Visit site (opens in a new tab)Reviewed 10 November 202643 issues · 78 checks

This review found 43 issues worth fixing on kaysalove.com, 17 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of kaysalove.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kaysalove.com at 0.6 s0.6 s
  2. kaysalove.com at 1.1 s1.1 s
  3. kaysalove.com at 1.7 s1.7 s
  4. kaysalove.com at 2.2 s2.2 s
  5. kaysalove.com at 2.8 s2.8 s
  6. kaysalove.com at 3.3 s3.3 s
  7. kaysalove.com at 3.9 s3.9 s
  8. kaysalove.com at 4.4 s4.4 s

Speed

9 to fix70
  • Use efficient cache lifetimes

    6.8 s · 2.1 MB

    25 files are served with short cache lifetimes, so returning visitors download them again (2.1 MB).

  • Improve image delivery

    5.5 s · 1.8 MB

    3 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.5 s faster on a phone.

  • Reduce unused JavaScript

    1.8 s · 294 KiB

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

  • Render-blocking requests

    1.0 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.0 s.

  • Mobile performance score: 70

    70/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and teepublic.com and others), adding 2.8 MB and 425 ms of main-thread time.

  • Google Tag Manager adds 177 ms

    177 ms

    Google Tag Manager costs a phone 177 ms of main-thread work and 355 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.

  • veldrive.com adds 0 ms

    0 ms

    veldrive.com costs a phone 0 ms of main-thread work and 1.9 MB 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.

  • teepublic.com adds 84 ms

    84 ms

    teepublic.com costs a phone 84 ms of main-thread work and 399 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.

  • Reduce unused CSS

    180 ms · 40 KiB

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

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.2 s

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

  • Server response: 347 ms

    347 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 13.0 s

    13.0 s

    Your largest element takes 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ARWANA855 Situs Link Alternatif Terpercaya dengan Fasilitas…”.

  • Time to Interactive: 13.0 s

    13.0 s

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

  • Speed Index: 4.5 s

    4.5 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 4 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 79 ms

    79 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix40
  • 1 image over 500 KB

    situs-link-alternatif-terpercaya-dengan-fasilitas-kelas-diam weighs 859 KiB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    519 KiB

    2 images are downloaded at several times the size a phone draws them, for example situs-link-alternatif-terpercaya-dengan-fasilitas-kelas-diam at 1,254 px wide, shown at 350 px. Resized copies would save about 519 KiB.

  • Page weight: 2.8 MB in 40 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 40 requests on a phone: images 2.0 MB (20), scripts 636 KiB (11) and fonts 142 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (1.2 MB) are 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.8 g of CO₂ per visit

    0.80 g

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

1 checks passed
  • Images load when needed

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

Accessibility

11 to fixGoogle 6784
  • 1 button without a name

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

  • 5 text elements with low contrast

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • 33 images without alt text

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

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

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

  • No main landmark

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

4 to fixGoogle 7776
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is long (73 characters)

    Your title is 73 characters, so Google will cut it off around 60: “ARWANA855 Situs Link Alternatif Terpercaya dengan Fasilitas Kelas Diamond”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“ARWANA855 Situs Link Alternatif Terpercaya dengan…” and “ARWANA855 Situs Link Alternatif Terpercaya dengan…”). One clear main headline is easier for people and search engines.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 120 internal links, 20 external

    The homepage links to 120 pages on kaysalove.com and 20 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.kaysalove.com/.

  • Structured data in place

    Structured data found: BreadcrumbList and FAQPage.

  • 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://www.kaysalove.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.kaysalove.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.

  • Opted out of AI training for 5 crawlers

    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.

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

  • Text is in the HTML

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

Other pages

1 to fix0
  • 15 linked pages are broken

    Your homepage links to https://www.kaysalove.com/order/status, https://www.kaysalove.com/contact, https://www.kaysalove.com/shipping, https://www.kaysalove.com/sizechart, https://www.kaysalove.com/about and https://www.kaysalove.com/intellectual-property-policy and 9 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 15 internal pages checked

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

Best practices

5 to fixGoogle 6969
  • 7 broken images

    7 images failed to load on a phone, for example https://assets.teepublic.com/assets/teepublicons/x_close_orange400-c1926221e50e7f6686d23ac344405449054e43f23d0f3306f15d8dfd546f999a.svg.

  • 5 small tap targets

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

  • 1 third-party cookie

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Unexpected end of input”.

  • 2 distorted images

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

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 1,037 words of copy

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

4 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Order Status”, “Contact Us” and “Artist Signup”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 39 testimonial or review blocks, 1 customer or partner logo, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies, 1 of them by other companies (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.

  • 7 other companies contacted

    Loading the homepage contacts 7 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 kaysalove.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
10 Shopify Products;Shopify;Shopify Plus
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on kaysalove.com, including 14 speed issues, 4 SEO issues and 2 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