Website review, no card needed

lycan-project.com logo

lycan-project.com website review

Visit site (opens in a new tab)Reviewed 7 November 202630 issues · 70 checks

This review found 30 issues worth fixing on lycan-project.com, 9 of them high impact, across 70 checks. The most urgent: improve image delivery. 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 lycan-project.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lycan-project.com at 0.4 s0.4 s
  2. lycan-project.com at 0.8 s0.8 s
  3. lycan-project.com at 1.1 s1.1 s
  4. lycan-project.com at 1.5 s1.5 s
  5. lycan-project.com at 1.9 s1.9 s
  6. lycan-project.com at 2.3 s2.3 s
  7. lycan-project.com at 2.6 s2.6 s
  8. lycan-project.com at 3.0 s3.0 s

Speed

8 to fix66
  • Improve image delivery

    2.5 s · 735 KiB

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

  • Main-thread work: 17.0 s

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

  • Reduce unused JavaScript

    810 ms · 397 KiB

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

  • Mobile performance score: 66

    66/100

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

  • Render-blocking requests

    700 ms

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

  • Shopify adds 201 ms

    201 ms

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

  • 3 long tasks on the main thread

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

  • 2,228 HTML elements

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Shopify, bestfreecdn.com and conversionbear.com and others), adding 860 KiB and 326 ms of main-thread time.

  • Use efficient cache lifetimes

    250 ms · 114 KiB

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

  • Reduce unused CSS

    12 KiB

    About 12 KiB of CSS is downloaded but never applied on this page.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

4 to fix66
  • Largest Contentful Paint: 12.1 s

    12.1 s

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

  • Time to Interactive: 12.9 s

    12.9 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • 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: 115 ms

    115 ms

    Scripts block the page for only 115 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

3 to fix68
  • Page weight: 3.5 MB in 398 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 398 requests on a phone: images 1.4 MB (28), other files 1.1 MB (205) and scripts 780 KiB (120). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    454 KiB

    6 images are downloaded at several times the size a phone draws them, for example IMG_20260724_131515.png at 2,000 px wide, shown at 360 px. Resized copies would save about 454 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (296 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (121 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 1.0 g of CO₂ per visit

    1.01 g

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

Accessibility

4 to fixGoogle 9795
  • 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.

  • Scrollable region must have keyboard access (1 element)

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

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 33 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

4 to fixGoogle 10079
  • Title is short (25 characters)

    Your title is only 25 characters: “Awruff Gear – AWRUFF GEAR”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Canonical points to another host

    Your canonical URL points to awruffgear.com, not lycan-project.com, so Google may credit that host instead.

  • Meta description is long (170 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 79 internal links, 18 external

    The homepage links to 79 pages on lycan-project.com and 18 external pages.

4 checks passed
  • 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://lycan-project.com/sitemap.xml.

AI search readiness

100
4 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, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix95
  • 9 pages without a meta description

    https://lycan-project.com/collections/all, https://lycan-project.com/policies/shipping-policy, https://lycan-project.com/collections/discover, https://lycan-project.com/collections/lanyard-tags, https://lycan-project.com/collections/keychains and https://lycan-project.com/collections/cards-badges and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7797
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    21 of 22 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 analytics detected

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

  • 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 250 words of copy

    The homepage carries about 250 words of visible text.

1 checks passed
  • 4 short forms

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

Privacy and tracking

  • 12 cookies set on arrival

    12

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 lycan-project.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 17 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Customeow Product Personalizer · Inbox · Keepcart Coupon Protect · Fly Bundles Upsells · Magical Vacations · Terms Checkbox · Uppromote Affiliate · King Product Options · Echo All In One Fixed Bundles · Terms And Conditions In Cart · Nova Multi Currency Converter · Simple Bundle · Checkout Regeln Grosse Warenkoerbe 2026 · Affliate By Secomapp · Appstle Bundles · conversionbear.com · bestfreecdn.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
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 lycan-project.com, including 12 speed issues, 4 SEO issues and 5 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