Website review, no card needed

skylrk.com logo

skylrk.com website review

Visit site (opens in a new tab)Reviewed 20 November 202630 issues · 74 checks

This review found 30 issues worth fixing on skylrk.com, 13 of them high impact, across 74 checks. The most urgent: main-thread work: 41.7 s. 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.6 s2.0 sMay 30Nov 142.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.4 s
Jun 6, 20262.5 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.3 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.1 s
Oct 10, 20262.2 s
Oct 17, 20262.3 s
Oct 24, 20262.2 s
Oct 31, 20262.1 s
Nov 7, 20262.1 s
Nov 14, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
266 ms164 msMay 30Nov 14176 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026230 ms
Jun 6, 2026243 ms
Jun 13, 2026244 ms
Jun 20, 2026250 ms
Jun 27, 2026251 ms
Jul 4, 2026249 ms
Jul 11, 2026254 ms
Jul 18, 2026243 ms
Jul 25, 2026231 ms
Aug 1, 2026232 ms
Aug 8, 2026231 ms
Aug 15, 2026229 ms
Aug 22, 2026230 ms
Aug 29, 2026219 ms
Sep 5, 2026215 ms
Sep 12, 2026203 ms
Sep 19, 2026203 ms
Sep 26, 2026201 ms
Oct 3, 2026194 ms
Oct 10, 2026194 ms
Oct 17, 2026190 ms
Oct 24, 2026184 ms
Oct 31, 2026182 ms
Nov 7, 2026182 ms
Nov 14, 2026176 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 skylrk.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. skylrk.com at 4.4 s4.4 s
  2. skylrk.com at 8.8 s8.8 s
  3. skylrk.com at 13.1 s13.1 s
  4. skylrk.com at 17.5 s17.5 s
  5. skylrk.com at 21.9 s21.9 s
  6. skylrk.com at 26.3 s26.3 s
  7. skylrk.com at 30.6 s30.6 s
  8. skylrk.com at 35.0 s35.0 s

Speed

7 to fix34
  • Main-thread work: 41.7 s

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

  • Signyfyd adds 2.8 s

    2.8 s

    Signyfyd costs a phone 2.8 s of main-thread work and 519 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused JavaScript

    1.2 s · 377 KiB

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

  • Mobile performance score: 34

    34/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Signyfyd, Shopify and Clarity and others), adding 1.4 MB and 3.5 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Render-blocking requests

    300 ms

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

  • Use efficient cache lifetimes

    150 ms · 110 KiB

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

  • Legacy JavaScript

    150 ms · 27 KiB

    Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Improve image delivery

    110 KiB

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

  • Minify JavaScript

    15 KiB

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

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

4 to fix100
  • Speed Index: 16.9 s

    16.9 s

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

  • Total Blocking Time: 21.7 s

    21.7 s

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

  • Time to Interactive: 41.7 s

    41.7 s

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

  • Largest Contentful Paint: 8.7 s

    8.7 s

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

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 173 ms

    173 ms

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

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

    1.3 s

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

  • Real-user TTFB: 604 ms

    604 ms

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

  • Tap response (INP) got 24% faster for real visitors

    -24%

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • First Contentful Paint: 1.8 s

    1.8 s

    The first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.3 MB in 190 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 190 requests on a phone: scripts 1.6 MB (104), images 318 KiB (21) and HTML 172 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.64 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

3 to fixGoogle 9694
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate 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
  • 37 automated accessibility rules passed

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

SEO

3 to fixGoogle 10078
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (6 characters)

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

  • Meta description is short (18 characters)

    Your meta description is only 18 characters: “OFFICIAL WEB STORE”. 70 to 160 characters is enough to sell the click.

  • 64 internal links, 2 external

    The homepage links to 64 pages on skylrk.com and 2 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://skylrk.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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://skylrk.com/sitemap.xml.

AI search readiness

100
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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.

  • llms.txt published

    The site publishes https://skylrk.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix74
  • 5 linked pages hidden from search

    https://skylrk.com/products/matterdaddies, https://skylrk.com/products/matterdaddies-pinky, https://skylrk.com/products/matterdaddies-4, https://skylrk.com/products/speed-demon-snow-camo and https://skylrk.com/products/glicky-gloss are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages share a title

    https://skylrk.com/products/matterdaddies, https://skylrk.com/products/matterdaddies-pinky and https://skylrk.com/products/matterdaddies-4 all use the title “MATTERDADDIES – SKYLRK”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://skylrk.com/pages/policies has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://skylrk.com/products/matterdaddies, https://skylrk.com/products/matterdaddies-toy, https://skylrk.com/products/matterdaddies-pinky and https://skylrk.com/products/matterdaddies-4 use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://skylrk.com/pages/contact, https://skylrk.com/pages/policies and https://skylrk.com/pages/wallpapers 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 31 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    14 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 title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 3 small tap targets

    3 of 13 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 “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'settings')”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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 direct contact details

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

  • Only about 28 words

    The homepage has only about 28 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop” and “Contact”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 7 cookies set on arrival

    7

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

  • 21 other companies contacted

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

Apps your storefront loads

Microsoft Clarity · Klaviyo Email Marketing Sms · Avada Order Limit · global-e.com · signifyd.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

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on skylrk.com, including 11 speed issues, 3 SEO issues and 4 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