Website review, no card needed

bekerfashions.com logo

bekerfashions.com website review

Visit site (opens in a new tab)Reviewed 20 November 202632 issues · 75 checks

This review found 32 issues worth fixing on bekerfashions.com, 8 of them high impact, across 75 checks. The most urgent: reduce unused JavaScript. 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
3.3 s1.1 sMay 30Nov 141.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.0 s
Jun 6, 20262.1 s
Jun 13, 20261.7 s
Jun 20, 20261.5 s
Jun 27, 20261.6 s
Jul 4, 20261.8 s
Jul 11, 20261.6 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.6 s
Aug 22, 20261.5 s
Aug 29, 20261.6 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.3 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Nov 7, 20261.5 s
Nov 14, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
175 ms74 msMay 30Nov 1489 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026163 ms
Jun 6, 2026145 ms
Jun 13, 2026131 ms
Jun 20, 2026126 ms
Jun 27, 2026120 ms
Jul 4, 2026126 ms
Jul 11, 2026112 ms
Jul 18, 2026104 ms
Jul 25, 2026104 ms
Aug 1, 202696 ms
Aug 8, 202695 ms
Aug 15, 202694 ms
Aug 22, 202687 ms
Aug 29, 202694 ms
Sep 5, 202695 ms
Sep 12, 2026102 ms
Sep 19, 202698 ms
Sep 26, 2026101 ms
Oct 3, 202695 ms
Oct 17, 202688 ms
Oct 24, 202686 ms
Oct 31, 202689 ms
Nov 7, 202696 ms
Nov 14, 202689 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 bekerfashions.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bekerfashions.com at 0.6 s0.6 s
  2. bekerfashions.com at 1.1 s1.1 s
  3. bekerfashions.com at 1.7 s1.7 s
  4. bekerfashions.com at 2.3 s2.3 s
  5. bekerfashions.com at 2.8 s2.8 s
  6. bekerfashions.com at 3.4 s3.4 s
  7. bekerfashions.com at 3.9 s3.9 s
  8. bekerfashions.com at 4.5 s4.5 s

Speed

10 to fix69
  • Reduce unused JavaScript

    1.9 s · 354 KiB

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

  • Use efficient cache lifetimes

    1.6 s · 330 KiB

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

  • Improve image delivery

    300 ms · 718 KiB

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

  • Mobile performance score: 69

    69/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, popt.in and Klaviyo and others), adding 1.1 MB and 284 ms of main-thread time.

  • Reduce unused CSS

    340 ms · 38 KiB

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

  • Render-blocking requests

    350 ms

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

  • 2,951 HTML elements

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

  • Main-thread work: 2.1 s

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

  • Shopify adds 87 ms

    87 ms

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

  • Legacy JavaScript

    200 ms · 25 KiB

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

  • 2 long tasks on the main thread

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

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

    10 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 10.8 s

    10.8 s

    Your largest element takes 10.8 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.8 s

    10.8 s

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

  • Speed Index: 5.6 s

    5.6 s

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

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

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: 1.4 s

    1.4 s

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

  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 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: 0.8 s

    0.8 s

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

  • Real-user TTFB: 329 ms

    329 ms

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

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

    -40%

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

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

    -43%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 22 ms

    22 ms

    Scripts block the page for only 22 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 4.9 MB in 456 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 456 requests on a phone: images 2.3 MB (102), other files 1.1 MB (197) and scripts 1.0 MB (127). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.38 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.38 g of CO₂e: 165.1 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 9495
  • ARIA commands must have an accessible name (5 elements)

    ARIA commands must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 261 images in the HTML carry an alt attribute.

  • 49 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: 49 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10074
  • No H1 headline

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

  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “FRASCARA – Evening Wear, Dresses, Gowns, Suits and Jumpsuits – Frascara”.

  • Meta description is long (313 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("/")”.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • 179 internal links, 7 external

    The homepage links to 179 pages on bekerfashions.com and 7 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.frascara.ca/.

  • 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://www.frascara.ca/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://www.frascara.ca/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix85
  • 8 pages without a meta description

    https://www.frascara.ca/pages/fw26, https://www.frascara.ca/pages/fw24, https://www.frascara.ca/collections/ready-to-wear, https://www.frascara.ca/collections/ready-to-wear/BEST-SELLER, https://www.frascara.ca/collections/ready-to-wear/DRESSES and https://www.frascara.ca/collections/ready-to-wear/GOWNS and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.frascara.ca/collections/ready-to-wear/BEST-SELLER, whose canonical is https://www.frascara.ca/collections/ready-to-wear/best-seller. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages without an H1

    https://www.frascara.ca/pages/ss26, https://www.frascara.ca/pages/ss27, https://www.frascara.ca/pages/fw26, https://www.frascara.ca/pages/fw25, https://www.frascara.ca/pages/ss25 and https://www.frascara.ca/pages/fw24 and 1 other 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 49 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 136 words

    The homepage has only about 136 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP COLLECTION”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “CONTACT”, “SHOP COLLECTION” and “SHOP GOWNS”.

  • 7 short forms

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta 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.

  • 16 cookies set on arrival

    16

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

  • 28 other companies contacted

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

Apps your storefront loads

Xo Gallery · Klaviyo Email Marketing Sms · popt.in · nfcube.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
AWS

Company

Headquarters
Toronto

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on bekerfashions.com, including 14 speed issues, 4 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