Website review, no card needed

lnkobrand.com logo

lnkobrand.com website review

Visit site (opens in a new tab)Reviewed 6 November 202626 issues · 75 checks

This review found 26 issues worth fixing on lnkobrand.com, 8 of them high impact, across 75 checks. The most urgent: page weight: 8.3 MB in 217 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

Real-visitor load time (LCP)75th percentile, phones
1.5 s915 msMay 16Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.0 s
May 23, 2026989 ms
May 30, 2026979 ms
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.2 s
Aug 22, 20261.3 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
132 ms99 msMay 16Oct 31103 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026113 ms
May 23, 2026118 ms
May 30, 2026121 ms
Jun 6, 2026128 ms
Jun 13, 2026128 ms
Jun 20, 2026123 ms
Jun 27, 2026121 ms
Jul 4, 2026120 ms
Jul 11, 2026119 ms
Jul 18, 2026120 ms
Jul 25, 2026113 ms
Aug 1, 2026112 ms
Aug 8, 2026112 ms
Aug 15, 2026112 ms
Aug 22, 2026116 ms
Aug 29, 2026117 ms
Sep 5, 2026122 ms
Sep 12, 2026120 ms
Sep 19, 2026116 ms
Sep 26, 2026119 ms
Oct 3, 2026111 ms
Oct 10, 2026111 ms
Oct 17, 2026111 ms
Oct 24, 2026105 ms
Oct 31, 2026103 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 lnkobrand.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lnkobrand.com at 0.7 s0.7 s
  2. lnkobrand.com at 1.5 s1.5 s
  3. lnkobrand.com at 2.2 s2.2 s
  4. lnkobrand.com at 3.0 s3.0 s
  5. lnkobrand.com at 3.7 s3.7 s
  6. lnkobrand.com at 4.5 s4.5 s
  7. lnkobrand.com at 5.2 s5.2 s
  8. lnkobrand.com at 6.0 s6.0 s

Speed

4 to fix65
  • Mobile performance score: 65

    65/100

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

  • Reduce unused JavaScript

    600 ms · 148 KiB

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

  • Main-thread work: 3.4 s

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

  • Render-blocking requests

    300 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (TikTok, Shopify and Klaviyo and others), adding 640 KiB and 253 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 40 KiB

    About 40 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.

  • Use efficient cache lifetimes

    150 ms · 37 KiB

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

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    29 KiB

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

  • Improve image delivery

    15 KiB

    1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 10.6 s

    10.6 s

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

  • Time to Interactive: 10.7 s

    10.7 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Largest content (LCP) got 19% slower for real visitors

    +19%

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

9 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: 1.7 s

    1.7 s

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

  • Real-user INP: 151 ms

    151 ms

    Real visitors wait 151 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.7 s

    1.7 s

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

  • Real-user TTFB: 587 ms

    587 ms

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

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

    -10%

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

  • Total Blocking Time: 68 ms

    68 ms

    Scripts block the page for only 68 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: 8.3 MB in 217 requests

    8.3 MB

    Your homepage downloads 8.3 MB in 217 requests on a phone: media 6.0 MB (1), other files 1.0 MB (113) and scripts 728 KiB (64). Under 2 MB keeps phones on slow connections fast.

  • About 2.3 g of CO₂ per visit

    2.35 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.35 g of CO₂e: 281.5 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 fixGoogle 8894
  • 18 text elements with low contrast

    18 text elements don'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.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

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

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

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

  • 76 internal links, 10 external

    The homepage links to 76 pages on lnkobrand.com and 10 external pages.

5 checks passed
  • Title: 54 characters

    Your title is a healthy 54 characters: “LNKO | Lunettes optique et solaires au Maroc à 650 dhs”.

  • Canonical URL set

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

  • 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://lnkobrand.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 (524 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix88
  • 8 pages without a meta description

    https://lnkobrand.com/collections/black-friday-26, https://lnkobrand.com/collections/black-friday26-30, https://lnkobrand.com/collections/black-friday-30, https://lnkobrand.com/collections/lnko-x-a-conic, https://lnkobrand.com/collections/solaire and https://lnkobrand.com/collections/optique and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://lnkobrand.com/products/sera-banana-breeze and https://lnkobrand.com/products/sera-pistachio-frost use the same meta description. A description written for each page earns more clicks.

  • 14 pages without an H1

    https://lnkobrand.com/collections/black-friday-26, https://lnkobrand.com/collections/black-friday26-30, https://lnkobrand.com/collections/black-friday-30, https://lnkobrand.com/collections/lnko-x-a-conic, https://lnkobrand.com/collections/solaire and https://lnkobrand.com/collections/femmes-solaire and 8 others 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 32 found) and read each the way a search engine does.

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

  • 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

2 to fixGoogle 10087
  • 14 small tap targets

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

  • 2 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 335 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop now” and “Contact information”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: TikTok Pixel.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 14 cookies set on arrival

    14

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

  • 18 other companies contacted

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

Apps your storefront loads

Parkour Tiktok Pixel · Klaviyo Email Marketing Sms · Musbu Wa Chat · Spin Wheel · nfcube.com · nice-team.net

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

Company

Employees
48
Headquarters
Casablanca

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 lnkobrand.com, including 8 speed issues, 3 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