Website review, no card needed

bydzyne.com logo

bydzyne.com website review

Visit site (opens in a new tab)Reviewed 27 October 202650 issues · 87 checks

This review found 50 issues worth fixing on bydzyne.com, 29 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
8.1 s4.5 sMay 9Oct 245.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20267.7 s
May 16, 20267.7 s
May 23, 20267.6 s
May 30, 20267.6 s
Jun 6, 20267.6 s
Jun 13, 20267.2 s
Jun 20, 20266.5 s
Jun 27, 20266.0 s
Jul 4, 20265.3 s
Jul 11, 20265.1 s
Jul 18, 20265.1 s
Jul 25, 20265.1 s
Aug 1, 20265.0 s
Aug 8, 20265.0 s
Aug 15, 20264.9 s
Aug 22, 20265.0 s
Aug 29, 20265.0 s
Sep 5, 20265.2 s
Sep 12, 20265.2 s
Sep 19, 20265.3 s
Sep 26, 20265.2 s
Oct 3, 20265.2 s
Oct 10, 20265.2 s
Oct 17, 20265.4 s
Oct 24, 20265.6 s
Real-visitor tap response (INP)75th percentile, phones
378 ms335 msMay 9Oct 24348 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026373 ms
May 16, 2026370 ms
May 23, 2026368 ms
May 30, 2026364 ms
Jun 6, 2026366 ms
Jun 13, 2026369 ms
Jun 20, 2026364 ms
Jun 27, 2026360 ms
Jul 4, 2026354 ms
Jul 11, 2026346 ms
Jul 18, 2026344 ms
Jul 25, 2026344 ms
Aug 1, 2026345 ms
Aug 8, 2026344 ms
Aug 15, 2026342 ms
Aug 22, 2026342 ms
Aug 29, 2026340 ms
Sep 5, 2026344 ms
Sep 12, 2026347 ms
Sep 19, 2026348 ms
Sep 26, 2026346 ms
Oct 3, 2026345 ms
Oct 10, 2026344 ms
Oct 17, 2026346 ms
Oct 24, 2026348 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 bydzyne.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bydzyne.com at 0.5 s0.5 s
  2. bydzyne.com at 1.1 s1.1 s
  3. bydzyne.com at 1.6 s1.6 s
  4. bydzyne.com at 2.2 s2.2 s
  5. bydzyne.com at 2.7 s2.7 s
  6. bydzyne.com at 3.2 s3.2 s
  7. bydzyne.com at 3.8 s3.8 s
  8. bydzyne.com at 4.3 s4.3 s

Speed

15 to fix33
  • Use efficient cache lifetimes

    43.6 s · 44.9 MB

    178 files are served with short cache lifetimes, so returning visitors download them again (44.9 MB).

  • Improve image delivery

    13.0 s · 19.3 MB

    57 images could be 19.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 13.0 s faster on a phone.

  • Render-blocking requests

    15.8 s

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

  • Reduce unused CSS

    8.6 s · 1.8 MB

    About 1.8 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 8.6 s faster on a phone.

  • Reduce unused JavaScript

    3.0 s · 2.7 MB

    About 2.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

  • YouTube adds 1.8 s

    1.8 s

    YouTube costs a phone 1.8 s of main-thread work and 3.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 33

    33/100

    Your mobile performance score is 33 (desktop: 28). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.8 s

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

  • 4,638 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, onelink-edge.com and Google Tag Manager and others), adding 45.5 MB and 2.8 s of main-thread time.

  • Amazon Web Services adds 0 ms

    0 ms

    Amazon Web Services costs a phone 0 ms of main-thread work and 41.3 MB 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.

  • onelink-edge.com adds 850 ms

    850 ms

    onelink-edge.com costs a phone 850 ms of main-thread work and 73 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.

  • 20 long tasks on the main thread

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

  • Document request latency

    476 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify JavaScript

    320 ms · 148 KiB

    148 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    200 ms · 34 KiB

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

  • Font display

    100 ms

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

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

    236 ms

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

Core Web Vitals

11 to fix33
  • 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.

  • Real-user LCP: 7.1 s

    7.1 s

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

  • Real-user INP: 563 ms

    563 ms

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

  • Real-user FCP: 6.2 s

    6.2 s

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

  • Real-user TTFB: 3.6 s

    3.6 s

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

  • First Contentful Paint: 19.4 s

    19.4 s

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

  • Largest Contentful Paint: 99.1 s

    99.1 s

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

  • Speed Index: 42.3 s

    42.3 s

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

  • Time to Interactive: 137.7 s

    137.7 s

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

  • Total Blocking Time: 963 ms

    963 ms

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

  • 42 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

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

3 checks passed
  • Real-user CLS: 0.05

    0.05

    For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.

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

    -29%

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

  • Cumulative Layout Shift: 0.044

    0.044

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

Images and page weight

5 to fix18
  • Page weight: 49.8 MB in 237 requests

    49.8 MB

    Your homepage downloads 49.8 MB in 237 requests on a phone: images 41.4 MB (147), scripts 4.6 MB (36) and stylesheets 2.0 MB (18). Under 2 MB keeps phones on slow connections fast.

  • 25 images over 500 KB

    25 images weigh 19.1 MB together. On a phone connection a single image that size takes seconds.

  • 18 images far larger than shown

    7.8 MB

    18 images are downloaded at several times the size a phone draws them, for example BDDV_Business.png at 1,080 px wide, shown at 226 px. Resized copies would save about 7.8 MB.

  • 40 images in older formats

    40 images (21.9 MB) are 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.

  • 22 images below the first screen load straight away

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

  • About 14.1 g of CO₂ per visit

    14.11 g

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

Accessibility

10 to fixGoogle 7386
  • Unlabelled dropdowns

    1 dropdown has no label.

  • Orphan list items

    Some list items are not inside a list.

  • 207 images without alt text

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

  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 169 form fields without a label

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

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

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

  • 44 links without text

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

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

4 to fixGoogle 6980
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

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

  • 4 H1 headlines

    There are 4 <h1> headlines (“ByDzyne App 3.0”, “ByDzyne App 3.0” and “ByDzyne App 3.0”). One clear main headline is easier for people and search engines.

  • 8 links crawlers can't follow

    8 links have no real href, so search engines can't follow them.

  • Open Graph partly set

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 61 internal links, 37 external

    The homepage links to 61 pages on bydzyne.com and 37 external pages.

4 checks passed
  • Title: 33 characters

    Your title is a healthy 33 characters: “ByDzyne: Products Inspired By You”.

  • Canonical URL set

    The canonical URL is https://www.bydzyne.com/Default.aspx.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at http://www.bydzyne.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.

  • No llms.txt

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

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

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 7797
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • A 96-field form

    Your longest form asks for 96 fields (0 required). Every extra field lowers completion.

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

  • About 1,021 words of copy

    The homepage carries about 1,021 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: “Join”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Sign up”, “Join” and “Shop”.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks, 58 trust badges and “50K Happy Customers”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 8 cookies set on arrival

    8

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

  • 13 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Vue.js
Analytics
Google Analytics
Hosting
AWS

Company

Founded
2019
Headquarters
Evanston

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on bydzyne.com, including 26 speed issues, 4 SEO issues and 2 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