Website review, no card needed
bimefy.com website review
Visit site (opens in a new tab)Reviewed 9 November 202629 issues · 72 checks
This review found 29 issues worth fixing on bimefy.com, 8 of them high impact, across 72 checks. The most urgent: page weight: 14.5 MB in 173 requests. 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
74CClosest competitors among SaaS websites
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
1.2 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Main-thread work: 5.2 s
A phone's processor spends 5.2 s on main-thread work while loading, 2.9 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 CDN, Clarity and eomail1.com and others), adding 9.8 MB and 504 ms of main-thread time.
Reduce unused JavaScript
900 ms · 357 KiBAbout 357 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
cloudfront.net adds 0 ms
0 mscloudfront.net costs a phone 0 ms of main-thread work and 9.4 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 374 ms. During a long task the page ignores taps.
Google CDN adds 291 ms
291 msGoogle CDN costs a phone 291 ms of main-thread work and 352 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.
Improve image delivery
309 KiB14 images could be 309 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
26 KiBAbout 26 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
10 KiB2 files are served with short cache lifetimes, so returning visitors download them again (10 KiB).
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: 146 ms
146 msYour server sent the HTML in 146 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 22.5 s
22.5 sThe page becomes fully interactive after 22.5 s. Good is under 3.8 s.
Largest Contentful Paint: 6.1 s
6.1 sYour largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s.
Total Blocking Time: 916 ms
916 msScripts block taps and scrolling for 916 ms in total while the page loads. Good is under 200 ms.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
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.
2 checks passed
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 14.5 MB in 173 requests
14.5 MBYour homepage downloads 14.5 MB in 173 requests on a phone: media 9.4 MB (1), scripts 2.1 MB (109) and other files 1.9 MB (14). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
49 KiB1 image is downloaded at several times the size a phone draws it, for example image at 1,622 px wide, shown at 215 px. Resized copies would save about 49 KiB.
About 4.1 g of CO₂ per visit
4.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.11 g of CO₂e: 492.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
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 31 images in the HTML carry an alt attribute.
SEO
5 H1 headlines
There are 5 <h1> headlines (“Connect reality to the plan,before problems becom…”, “Integrations” and “Tailored solutions for every role”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
45 internal links, 8 external
The homepage links to 45 pages on bimefy.com and 8 external pages.
6 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “Bimefy connects BIM, planning, cameras, reality capture and site data — so construction teams see problems before they …”.
Title: 48 characters
Your title is a healthy 48 characters: “Construction Site Intelligence Platform | Bimefy”.
Canonical URL set
The canonical URL is https://www.bimefy.com/.
Structured data in place
Structured data found: Organization.
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://www.bimefy.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.bimefy.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.
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (808 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.bimefy.com/converter and https://www.bimefy.com/booking all use the title “Bimefy - AI-driven BIM collaboration & progress monitoring”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages share a meta description
https://www.bimefy.com/pricing, https://www.bimefy.com/contact, https://www.bimefy.com/converter, https://www.bimefy.com/booking, https://www.bimefy.com/docs and https://www.bimefy.com/terms and 1 other use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://www.bimefy.com/booking has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.bimefy.com/contact, https://www.bimefy.com/converter and https://www.bimefy.com/booking 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 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 15 pages that loaded have a meta description.
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
3 small tap targets
3 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
About 842 words of copy
The homepage carries about 842 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get started with our free plan” and “Check the interactive demo now”.
14 calls to action
The homepage has 14 calls to action, for example “Pricing”, “Contact” and “Book Demo”.
Social proof on the page
Social proof on the homepage: 10 customer or partner logos and 1 trust badge.
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 tracker load before any consent
1Before a visitor clicks anything, the page loads Microsoft Clarity (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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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 bimefy.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
- Next.js
- Hosting
- AWS
Hiring
- Hiring
- 3 open roles
- Job board
- careers page
- Careers page
- login.bimefy.com/en/jobs (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on bimefy.com, including 13 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.