Website review, no card needed

lixpen.com logo

lixpen.com website review

Visit site (opens in a new tab)Reviewed 10 November 202626 issues · 70 checks

This review found 26 issues worth fixing on lixpen.com, 7 of them high impact, across 70 checks. The most urgent: render-blocking requests. 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 lixpen.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix92
  • Render-blocking requests

    1.3 s

    15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.

  • Reduce unused JavaScript

    322 KiB

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

  • ZenDesk adds 238 ms

    238 ms

    ZenDesk costs a phone 238 ms of main-thread work and 452 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.

  • 7 third-party services on the page

    7 third-party services load with your homepage (ZenDesk, Google Tag Manager and Google Analytics and others), adding 733 KiB and 344 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Reduce unused CSS

    20 ms · 21 KiB

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

  • Improve image delivery

    37 KiB

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

  • Use efficient cache lifetimes

    21 KiB

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

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

3 checks passed
  • Mobile performance score: 92

    92/100

    Your mobile performance score is 92. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.2 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

3 to fix92
  • Time to Interactive: 7.7 s

    7.7 s

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

  • Largest Contentful Paint: 3.0 s

    3.0 s

    Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LITTLE THINGS CAN DO BIGGER IDEAS”.

  • Speed Index: 3.7 s

    3.7 s

    Visually, the page fills in at 3.7 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.

3 checks passed
  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Total Blocking Time: 69 ms

    69 ms

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

1 to fix70
  • Page weight: 11.8 MB in 124 requests

    11.8 MB

    Your homepage downloads 11.8 MB in 124 requests on a phone: media 10.0 MB (2), scripts 780 KiB (29) and other files 658 KiB (66). Under 2 MB keeps phones on slow connections fast.

  • About 3.4 g of CO₂ per visit

    3.35 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.35 g of CO₂e: 402.3 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

4 to fix83
  • 1 image without alt text

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

  • 30 text elements with low contrast

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

  • 7 links without text

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

SEO

5 to fixGoogle 10079
  • Title is short (26 characters)

    Your title is only 26 characters: “Lix Pen – LixV3GlobalStore”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is short (51 characters)

    Your meta description is only 51 characters: “The smallest circular 3d printing pen in the world!”. 70 to 160 characters is enough to sell the click.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 19 internal links, 12 external

    The homepage links to 19 pages on lixpen.com and 12 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Little things cando bigger ideas”.

  • Canonical URL set

    The canonical URL is https://lixpen.com/.

  • 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://lixpen.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.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://lixpen.com/close, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages without a meta description

    https://lixpen.com/pages/art-marketplace and https://lixpen.com/pages/lix-pen-uv have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 internal pages checked

    We fetched 4 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • 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 3 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7776
  • 1 broken image

    1 image failed to load on a phone, for example https://lixpen.com/cdn/shop/t/4/assets/indexCompo.png?v=135.

  • Deprecated browser APIs

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    11 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

  • Only about 192 words

    The homepage has only about 192 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.

  • Urgency cues

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “START SHOPPING”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “learn more”, “Learn More” and “Shop now”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 3 email links.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 9 cookies set on arrival

    9

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

  • 14 other companies contacted

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

Apps on your store

No apps were seen in the code your storefront loads.

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

Framework
jQuery
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 26 issues on lixpen.com, including 6 speed issues, 5 SEO issues and 3 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