Website review, no card needed

bybrik.com logo

bybrik.com website review

Visit site (opens in a new tab)Reviewed 7 November 202637 issues · 82 checks

This review found 37 issues worth fixing on bybrik.com, 13 of them high impact, across 82 checks. The most urgent: 4 images over 500 KB. 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.3 s735 msMay 16Oct 31914 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026868 ms
May 23, 2026830 ms
May 30, 20261.1 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 2026958 ms
Jul 4, 2026820 ms
Jul 11, 2026806 ms
Jul 18, 2026808 ms
Jul 25, 2026812 ms
Aug 1, 2026845 ms
Aug 8, 2026877 ms
Aug 15, 2026890 ms
Aug 22, 2026914 ms
Aug 29, 2026905 ms
Sep 5, 2026901 ms
Sep 12, 2026916 ms
Sep 19, 2026914 ms
Sep 26, 2026924 ms
Oct 3, 2026943 ms
Oct 10, 2026934 ms
Oct 17, 2026925 ms
Oct 24, 2026928 ms
Oct 31, 2026914 ms
Real-visitor tap response (INP)75th percentile, phones
141 ms98 msMay 16Oct 31131 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026104 ms
May 23, 2026103 ms
May 30, 2026112 ms
Jun 6, 2026120 ms
Jun 13, 2026126 ms
Jun 20, 2026129 ms
Jun 27, 2026124 ms
Jul 4, 2026120 ms
Jul 11, 2026117 ms
Jul 18, 2026119 ms
Jul 25, 2026120 ms
Aug 1, 2026124 ms
Aug 8, 2026128 ms
Aug 15, 2026132 ms
Aug 22, 2026136 ms
Aug 29, 2026136 ms
Sep 5, 2026135 ms
Sep 12, 2026135 ms
Sep 19, 2026134 ms
Sep 26, 2026133 ms
Oct 3, 2026130 ms
Oct 10, 2026129 ms
Oct 17, 2026129 ms
Oct 24, 2026129 ms
Oct 31, 2026131 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 bybrik.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bybrik.com at 0.9 s0.9 s
  2. bybrik.com at 1.7 s1.7 s
  3. bybrik.com at 2.6 s2.6 s
  4. bybrik.com at 3.5 s3.5 s
  5. bybrik.com at 4.3 s4.3 s
  6. bybrik.com at 5.2 s5.2 s
  7. bybrik.com at 6.1 s6.1 s
  8. bybrik.com at 6.9 s6.9 s

Speed

8 to fix52
  • Improve image delivery

    2.2 s · 570 KiB

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

  • Main-thread work: 5.3 s

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

  • Mobile performance score: 52

    52/100

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

  • 7 long tasks on the main thread

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

  • Render-blocking requests

    900 ms

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

  • Reduce unused JavaScript

    300 ms · 150 KiB

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

  • 2,898 HTML elements

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

  • Shopify adds 177 ms

    177 ms

    Shopify costs a phone 177 ms of main-thread work and 341 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 (Clarity, Shopify and nfcube.com and others), adding 457 KiB and 372 ms of main-thread time.

  • Use efficient cache lifetimes

    76 KiB

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

  • Duplicated JavaScript

    66 KiB

    66 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    11 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

9 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Largest Contentful Paint: 51.6 s

    51.6 s

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

  • Time to Interactive: 57.2 s

    57.2 s

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

  • Speed Index: 10.8 s

    10.8 s

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

  • Real-user INP: 203 ms

    203 ms

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

  • Tap response (INP) got 26% slower for real visitors

    +26%

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

  • Total Blocking Time: 479 ms

    479 ms

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • 11 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

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

    1.1 s

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

  • Real-user TTFB: 513 ms

    513 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

5 to fix29
  • 4 images over 500 KB

    4 images weigh 42.7 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 34.3 MB in 283 requests

    34.3 MB

    Your homepage downloads 34.3 MB in 283 requests on a phone: images 18.3 MB (70), media 14.5 MB (4) and other files 778 KiB (111). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    7.0 MB

    2 images are downloaded at several times the size a phone draws them, for example Untitled_design.svg at 1,440 px wide, shown at 386 px. Resized copies would save about 7.0 MB.

  • 6 images below the first screen load straight away

    6 images further down the page (20.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    04e30efbfcd7dfca630b9f379212f3cb7e0b04a9_1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

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

    9.73 g

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

Accessibility

7 to fixGoogle 8990
  • 5 buttons without a name

    5 buttons have no accessible name, so screen readers announce just “button”.

  • 7 text elements with low contrast

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

  • Interactive controls must not be nested (3 elements)

    Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

  • 4 images without alt text

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

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

    All page content should be contained by landmarks: 3 elements on the page fail 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.

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

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

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 10088
  • Title is short (12 characters)

    Your title is only 12 characters: “brïk – brïk.”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • One H1 headline

    Your <h1> is empty.

  • 179 internal links, 9 external

    The homepage links to 179 pages on bybrik.com and 9 external pages.

6 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Three years of brïk, and we’re onto something new. Pattern Play is coming soon — our 3rd Anniversary Collection of play…”.

  • Canonical URL set

    The canonical URL is https://bybrik.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://bybrik.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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, 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 (1,362 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 8 pages without a meta description

    https://bybrik.com/collections/all-products, https://bybrik.com/policies/shipping-policy, https://bybrik.com/collections/pattern-play, https://bybrik.com/collections/sundae-bag, https://bybrik.com/collections/pixie-bag and https://bybrik.com/collections/posie-bag and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://bybrik.com/collections/all-products, https://bybrik.com/collections/pattern-play, https://bybrik.com/collections/sundae-bag, https://bybrik.com/collections/pixie-bag, https://bybrik.com/collections/posie-bag and https://bybrik.com/collections/cardi-knit and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://bybrik.com/collections/pixie-bag, https://bybrik.com/collections/posie-bag, https://bybrik.com/collections/cardi-knit and https://bybrik.com/collections/pattern-play-accessories took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

  • 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 8 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 9 small tap targets

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

  • 3 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 300 words of copy

    The homepage carries about 300 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop now”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop all”, “shop now” and “shop our birthday collection!”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 6 customer or partner logos, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.

  • 15 cookies set on arrival

    15

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

  • 27 other companies contacted

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

Apps your storefront loads

Pagefly Ai Page Builder · Geolocation Glc · Microsoft Clarity · Judge Me Reviews · Orbe Geolocation · nfcube.com · herokuapp.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

Hiring

Hiring
4 open roles
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on bybrik.com, including 17 speed issues, 2 SEO issues and 1 conversion gap. 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