Website review, no card needed
bunkr.cr website review
Visit site (opens in a new tab)Reviewed 11 October 202614 issues · 58 checks
This review found 14 issues worth fixing on bunkr.cr, 2 of them high impact, across 58 checks. The most urgent: no calls to action. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 954 ms |
| Apr 25, 2026 | 954 ms |
| May 2, 2026 | 1.0 s |
| May 9, 2026 | 1.0 s |
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 983 ms |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 989 ms |
| Jul 4, 2026 | 949 ms |
| Jul 11, 2026 | 926 ms |
| Jul 18, 2026 | 925 ms |
| Jul 25, 2026 | 922 ms |
| Aug 1, 2026 | 915 ms |
| Aug 8, 2026 | 917 ms |
| Aug 15, 2026 | 915 ms |
| Aug 22, 2026 | 916 ms |
| Aug 29, 2026 | 929 ms |
| Sep 5, 2026 | 977 ms |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 155 ms |
| Apr 25, 2026 | 155 ms |
| May 2, 2026 | 150 ms |
| May 9, 2026 | 148 ms |
| May 16, 2026 | 146 ms |
| May 23, 2026 | 144 ms |
| May 30, 2026 | 149 ms |
| Jun 6, 2026 | 151 ms |
| Jun 13, 2026 | 151 ms |
| Jun 20, 2026 | 151 ms |
| Jun 27, 2026 | 150 ms |
| Jul 4, 2026 | 149 ms |
| Jul 11, 2026 | 149 ms |
| Jul 18, 2026 | 149 ms |
| Jul 25, 2026 | 150 ms |
| Aug 1, 2026 | 152 ms |
| Aug 8, 2026 | 153 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 151 ms |
| Aug 29, 2026 | 148 ms |
| Sep 5, 2026 | 145 ms |
| Sep 12, 2026 | 143 ms |
| Sep 19, 2026 | 141 ms |
| Sep 26, 2026 | 141 ms |
| Oct 3, 2026 | 141 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
Speed
Use efficient cache lifetimes
48 KiB6 files are served with short cache lifetimes, so returning visitors download them again (48 KiB).
2 third-party services on the page
2 third-party services load with your homepage (Cloudflare and northstar.cr), adding 17 KiB and 10 ms of main-thread time.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 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.
3 checks passed
Mobile performance score: 100
100/100Your mobile performance score is 100 (desktop: 100). That is in Google's “good” band (90 and up).
Main-thread work: 0.1 s
A phone's processor spends 0.1 s on main-thread work while loading, 22 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 155 ms to 141 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
12 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: 0.6 s
0.6 sReal visitors wait 0.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 78 ms
78 msReal visitors wait 78 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 369 ms
369 msReal visitors wait 369 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.011
0.011The layout barely moves while loading (CLS 0.011, good is under 0.1).
Largest Contentful Paint: 1.5 s
1.5 sYour largest element renders in 1.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “The free-for-all File Hosting.”.
Speed Index: 1.5 s
1.5 sVisually, the page fills in at 1.5 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 1.5 s
1.5 sThe page is fully interactive after 1.5 s.
Images and page weight
About 0.02 g of CO₂ per visit
0.02 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.02 g of CO₂e: 2.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 79 KiB in 9 requests
79 KiBYour homepage downloads 79 KiB in 9 requests on a phone: fonts 44 KiB (2), scripts 17 KiB (2) and stylesheets 11 KiB (1). That is a lean page.
Accessibility
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.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 checks passed
Every image has alt text
All 4 images in the HTML carry an alt attribute.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (53 characters)
Your meta description is only 53 characters: “Bunkr - Your trusted free privacy-aware file hosting.”. 70 to 160 characters is enough to sell the click.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://bunkr.cr/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at bunkr.cr/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
5 internal links, 3 external
The homepage links to 5 pages on bunkr.cr and 3 external pages.
3 checks passed
One H1 headline
Your main headline reads: “The free-for-all File Hosting.”.
Title: 36 characters
Your title is a healthy 36 characters: “BUNKR - Privacy-focused File Hosting”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
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://bunkr.cr/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.
1 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Other pages
2 pages share a meta description
https://bunkr.cr/upload and https://bunkr.cr/auth use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://bunkr.cr/auth has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://bunkr.cr/faq, https://bunkr.cr/upload and https://bunkr.cr/auth have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
3 internal pages checked
We fetched 3 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 3 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 3 pages that loaded have a meta description.
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 3 pages that loaded have a <title>.
Best practices
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 38 words
The homepage has only about 38 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
1 checks passed
Analytics in place
Analytics detected: Cloudflare Web Analytics.
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 bunkr.cr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 14 issues on bunkr.cr, including 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.