Website review, no card needed

bitis.com.vn logo

bitis.com.vn website review

Visit site (opens in a new tab)Reviewed 19 October 202639 issues · 82 checks

This review found 39 issues worth fixing on bitis.com.vn, 16 of them high impact, across 82 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
2.6 s1.1 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.5 s
May 9, 20261.4 s
May 16, 20261.6 s
May 23, 20261.7 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.7 s
Jun 20, 20261.5 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.4 s
Aug 29, 20261.5 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.7 s
Sep 26, 20261.9 s
Oct 3, 20262.1 s
Oct 10, 20262.3 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
193 ms123 msMay 2Oct 17164 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026177 ms
May 9, 2026167 ms
May 16, 2026171 ms
May 23, 2026178 ms
May 30, 2026185 ms
Jun 6, 2026184 ms
Jun 13, 2026179 ms
Jun 20, 2026175 ms
Jun 27, 2026169 ms
Jul 4, 2026171 ms
Jul 11, 2026171 ms
Jul 18, 2026171 ms
Jul 25, 2026172 ms
Aug 1, 2026170 ms
Aug 8, 2026171 ms
Aug 15, 2026155 ms
Aug 22, 2026136 ms
Aug 29, 2026131 ms
Sep 5, 2026132 ms
Sep 12, 2026141 ms
Sep 19, 2026154 ms
Sep 26, 2026161 ms
Oct 3, 2026162 ms
Oct 10, 2026162 ms
Oct 17, 2026164 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 bitis.com.vn (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bitis.com.vn at 1.2 s1.2 s
  2. bitis.com.vn at 2.4 s2.4 s
  3. bitis.com.vn at 3.7 s3.7 s
  4. bitis.com.vn at 4.9 s4.9 s
  5. bitis.com.vn at 6.1 s6.1 s
  6. bitis.com.vn at 7.3 s7.3 s
  7. bitis.com.vn at 8.5 s8.5 s
  8. bitis.com.vn at 9.7 s9.7 s

Speed

13 to fix48
  • Improve image delivery

    3.6 s · 1.3 MB

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

  • Use efficient cache lifetimes

    1.6 s · 294 KiB

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

  • Reduce unused JavaScript

    1.1 s · 735 KiB

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

  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 48

    48/100

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

  • Main-thread work: 4.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, hstatic.net and Facebook and others), adding 4.1 MB and 1.7 s of main-thread time.

  • Google Tag Manager adds 935 ms

    935 ms

    Google Tag Manager costs a phone 935 ms of main-thread work and 1,007 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.

  • hstatic.net adds 371 ms

    371 ms

    hstatic.net costs a phone 371 ms of main-thread work and 2.6 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.

  • Reduce unused CSS

    300 ms · 83 KiB

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

  • 13 long tasks on the main thread

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

  • Facebook adds 215 ms

    215 ms

    Facebook costs a phone 215 ms of main-thread work and 308 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.

  • 2,369 HTML elements

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

  • Legacy JavaScript

    150 ms · 55 KiB

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

  • Minify JavaScript

    18 KiB

    18 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    13 KiB

    13 KiB JavaScript is shipped twice across bundles.

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

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

    446 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 11.6 s

    11.6 s

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

  • Time to Interactive: 23.3 s

    23.3 s

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

  • Speed Index: 9.8 s

    9.8 s

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

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

    +64%

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

  • Total Blocking Time: 562 ms

    562 ms

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

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

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

7 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.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 INP: 138 ms

    138 ms

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

    1.4 s

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

  • Real-user TTFB: 705 ms

    705 ms

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

2 to fix60
  • Page weight: 4.2 MB in 122 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 122 requests on a phone: scripts 1.9 MB (36), images 1.8 MB (41) and fonts 313 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    355 KiB

    6 images are downloaded at several times the size a phone draws them, for example artboard_1_dfe3e3cfcb994a30b7a6467facd14a46.png at 1,440 px wide, shown at 390 px. Resized copies would save about 355 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (76 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.20 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 8391
  • 22 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

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

SEO

2 to fixGoogle 10086
  • No H1 headline

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

  • No structured data

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

  • Open Graph partly set

    Open Graph is missing og:title, 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.

  • 175 internal links, 4 external

    The homepage links to 175 pages on bitis.com.vn and 4 external pages.

5 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “Trang bán hàng chính thức trực thuộc công ty TNHH Bình Tiên (Biti’s), kênh bán hàng trực tuyến sản phẩm giày dép Biti's…”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Trang bán hàng trực tuyến của Biti's Việt Nam”.

  • Canonical URL set

    The canonical URL is https://bitis.com.vn/.

  • 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://bitis.com.vn/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://bitis.com.vn/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 (1,113 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 91 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

2 to fixGoogle 9691
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 503 ()”.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • A 9-field form

    Your longest form asks for 9 fields (2 required). Every extra field lowers completion.

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

    The homepage carries about 491 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 8 cookies set on arrival

    8

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

  • 14 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on bitis.com.vn, including 20 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