Website review, no card needed

dat.bike logo

dat.bike website review

Visit site (opens in a new tab)Reviewed 4 November 202638 issues · 75 checks

This review found 38 issues worth fixing on dat.bike, 17 of them high impact, across 75 checks. The most urgent: improve image delivery. 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.0 s1.5 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.4 s
Jul 25, 20262.5 s
Aug 1, 20262.6 s
Aug 8, 20262.7 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.7 s
Sep 26, 20262.6 s
Oct 3, 20262.3 s
Oct 10, 20262.1 s
Oct 17, 20261.9 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
358 ms200 msMay 16Oct 31229 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026340 ms
May 23, 2026336 ms
May 30, 2026272 ms
Jun 6, 2026243 ms
Jun 13, 2026226 ms
Jun 20, 2026218 ms
Jun 27, 2026228 ms
Jul 4, 2026237 ms
Jul 11, 2026246 ms
Jul 18, 2026254 ms
Jul 25, 2026262 ms
Aug 1, 2026272 ms
Aug 8, 2026285 ms
Aug 15, 2026299 ms
Aug 22, 2026310 ms
Aug 29, 2026313 ms
Sep 5, 2026314 ms
Sep 12, 2026313 ms
Sep 19, 2026312 ms
Sep 26, 2026301 ms
Oct 3, 2026278 ms
Oct 10, 2026260 ms
Oct 17, 2026238 ms
Oct 24, 2026230 ms
Oct 31, 2026229 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 dat.bike (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dat.bike at 0.8 s0.8 s
  2. dat.bike at 1.6 s1.6 s
  3. dat.bike at 2.5 s2.5 s
  4. dat.bike at 3.3 s3.3 s
  5. dat.bike at 4.1 s4.1 s
  6. dat.bike at 4.9 s4.9 s
  7. dat.bike at 5.8 s5.8 s
  8. dat.bike at 6.6 s6.6 s

Speed

10 to fix48
  • Improve image delivery

    3.1 s · 1.5 MB

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

  • Reduce unused JavaScript

    2.9 s · 474 KiB

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

  • Render-blocking requests

    2.0 s

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

  • Use efficient cache lifetimes

    1.1 s · 289 KiB

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

  • Mobile performance score: 48

    48/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, TikTok and Facebook and others), adding 1.0 MB and 1.3 s of main-thread time.

  • Google Tag Manager adds 757 ms

    757 ms

    Google Tag Manager costs a phone 757 ms of main-thread work and 528 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.

  • 10 long tasks on the main thread

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

  • Legacy JavaScript

    350 ms · 23 KiB

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

  • Main-thread work: 2.6 s

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

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

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

8 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: 29.4 s

    29.4 s

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

  • Time to Interactive: 30.2 s

    30.2 s

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

  • Speed Index: 12.3 s

    12.3 s

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

  • Total Blocking Time: 610 ms

    610 ms

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

  • Real-user INP: 250 ms

    250 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 2 images without width and height

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

7 checks passed
  • 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 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: 785 ms

    785 ms

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

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

    -32%

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

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

    -29%

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

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

5 to fix18
  • Page weight: 13.0 MB in 113 requests

    13.0 MB

    Your homepage downloads 13.0 MB in 113 requests on a phone: images 11.2 MB (47), scripts 1.1 MB (18) and fonts 616 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 9 images over 500 KB

    9 images weigh 8.0 MB together. On a phone connection a single image that size takes seconds.

  • 16 images far larger than shown

    2.9 MB

    16 images are downloaded at several times the size a phone draws them, for example image-1.png at 1,537 px wide, shown at 358 px. Resized copies would save about 2.9 MB.

  • 26 images below the first screen load straight away

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

  • 10 images in older formats

    10 images (7.7 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.

  • About 3.7 g of CO₂ per visit

    3.68 g

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

Accessibility

3 to fixGoogle 9194
  • 2 buttons without a name

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

  • 2 text elements with low contrast

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

  • 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 52 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

2 to fixGoogle 10092
  • Meta description is long (166 characters)

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

  • No social preview image

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

  • 59 internal links, 3 external

    The homepage links to 59 pages on dat.bike and 3 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Đủ Thực lựcCân Đời Thực”.

  • Title: 31 characters

    Your title is a healthy 31 characters: “Xe máy điện Dat Bike - Dat Bike”.

  • Canonical URL set

    The canonical URL is https://dat.bike/.

  • Structured data in place

    Structured data found: Article, BreadcrumbList, ImageObject, Organization and Person.

  • 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://dat.bike/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

    The site publishes https://dat.bike/llms.txt (84 KiB, 154 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix85
  • 3 pages without a meta description

    https://dat.bike/era, https://dat.bike/ve-dat-bike and https://dat.bike/category/tin-tuc/tin-tuc-su-kien have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://dat.bike/category/tin-tuc/tin-tuc-su-kien, whose canonical is https://dat.bike/category/tin-tuc-su-kien. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://dat.bike/era has 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 26 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 7796
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

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

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 68 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 1,022 words of copy

    The homepage carries about 1,022 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 12 cookies set on arrival

    12

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

  • 23 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
10 Shopify Products;Shopify;Shopify Plus;Webflow Ecommerce
Analytics
Google Tag Manager
Hosting
Vnpt As Vn Vietnam Posts And Telecommunications Group

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on dat.bike, including 18 speed issues, 2 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