Website review, no card needed

rebillify.io logo

rebillify.io website review

Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 80 checks

This review found 36 issues worth fixing on rebillify.io, 14 of them high impact, across 80 checks. The most urgent: render-blocking requests. 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

Full-page screenshot of rebillify.io (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rebillify.io at 1.6 s1.6 s
  2. rebillify.io at 3.1 s3.1 s
  3. rebillify.io at 4.7 s4.7 s
  4. rebillify.io at 6.2 s6.2 s
  5. rebillify.io at 7.8 s7.8 s
  6. rebillify.io at 9.4 s9.4 s
  7. rebillify.io at 10.9 s10.9 s
  8. rebillify.io at 12.5 s12.5 s

Speed

11 to fix31
  • Render-blocking requests

    3.2 s

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

  • Reduce unused CSS

    1.6 s · 323 KiB

    About 323 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Mobile performance score: 31

    31/100

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

  • 4,638 HTML elements

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

  • Use efficient cache lifetimes

    500 ms · 528 KiB

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

  • Font display

    900 ms

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

  • Improve image delivery

    742 KiB

    15 images could be 742 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 7 long tasks on the main thread

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, bongdalumoi.win and Cloudflare and others), adding 2.2 MB and 226 ms of main-thread time.

  • Main-thread work: 3.7 s

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

  • cloudfront.net adds 0 ms

    0 ms

    cloudfront.net costs a phone 0 ms of main-thread work and 1.5 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 JavaScript

    234 KiB

    About 234 KiB of JavaScript is downloaded but never used on this page.

  • Minify CSS

    150 ms · 29 KiB

    29 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 224 ms

    224 ms

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

Core Web Vitals

6 to fix27
  • Cumulative Layout Shift: 0.951

    0.951

    The layout shifts by 0.951 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 17.3 s

    17.3 s

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

  • Largest Contentful Paint: 5.3 s

    5.3 s

    Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Bongdalu hiện khẳng định vững chắc vị thế là một trong nhữn…”.

  • Speed Index: 7.2 s

    7.2 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Total Blocking Time: 514 ms

    514 ms

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

2 to fix60
  • Page weight: 4.3 MB in 195 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 195 requests on a phone: images 2.2 MB (89), scripts 654 KiB (42) and other files 548 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    210 KiB

    1 image is downloaded at several times the size a phone draws it, for example logo-bongdalu.png at 1,024 px wide, shown at 188 px. Resized copies would save about 210 KiB.

  • 1 image in older formats

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

    1.22 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 8593
  • 83 text elements with low contrast

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

  • 6 images without alt text

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

  • 3 links without text

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

  • 2 form fields without a label

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

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

1 checks passed
  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 3 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 7793
  • 2 H1 headlines

    There are 2 <h1> headlines (“Bongdalu ⚽ Tỷ Số Bóng Đá & Tỷ Lệ Kèo | KQBD Trực …” and “Bongdalu – Tổng Quan Về Nền Tảng Dữ Liệu Bóng Đá …”). One clear main headline is easier for people and search engines.

  • 2 links crawlers can't follow

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

  • 26 internal links, 5 external

    The homepage links to 26 pages on rebillify.io and 5 external pages.

7 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Bongdalu cập nhật tỷ số bóng đá, livescore, tỷ lệ kèo và KQBD hôm nay chuẩn xác 24/7. Đồng bộ dữ liệu hơn 1.500 giải đấ…”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Bongdalu - Xem Tỷ Số & Tỷ Lệ Kèo Bóng Đá | KQBD Hôm Nay”.

  • Canonical URL set

    The canonical URL is https://cccdigital.io/vi-vn/.

  • Structured data in place

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

  • 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://cccdigital.io/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://cccdigital.io/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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,137 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 2 pages without a meta description

    https://cccdigital.io/kien-thuc-bong-da and https://cccdigital.io/tin-tuc-the-thao have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 links to non-canonical URLs

    Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://cccdigital.io/kien-thuc-bong-da, whose canonical is https://cccdigital.io/vi-vn/kien-thuc-bong-da. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    https://cccdigital.io/ty-le-keo, https://cccdigital.io/ket-qua-bong-da, https://cccdigital.io/lich-thi-dau, https://cccdigital.io/tips and https://cccdigital.io/kho-du-lieu have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://cccdigital.io/tin-tuc-the-thao and https://cccdigital.io/ty-le-keo took over 3 s to send their HTML from our server.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 12 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 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 16 small tap targets

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

  • 2 JavaScript errors while loading

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix56
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 2,919 words of copy

    The homepage carries about 2,919 words of visible text.

3 checks passed
  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 2 cookies set on arrival

    2

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 rebillify.io, 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
Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on rebillify.io, including 17 speed issues, 2 SEO issues and 5 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