builderall.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user INP: 513 ms

  513 ms

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

• Real-user FCP: 1.9 s

  1.9 s

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

• Tap response (INP) held steady for real visitors

  +8%

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

• Page weight: 6.7 MB

  6.7 MB

  Your homepage downloads 6.7 MB on a phone, 4.6 MB of it images (70%). Under 2 MB keeps phones on slow connections fast.

• 14 images far larger than shown

  1.8 MB

  14 images are downloaded at several times the size a phone draws them, for example 627b0cf6f15a314dfdb2f706db536b6afe7cb89a14bb142ce7861cef972f at 1,202 px wide, shown at 180 px. Resized copies would save about 1.8 MB.

  Elements (5)

• 1 image over 500 KB

  rectangle-42-327-154.png weighs 782 KiB. On a phone connection a single image that size takes seconds.

  Elements (1)

• 19 images in older formats

  19 images (3.2 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.

  Elements (5)

• 11 images below the first screen load straight away

  11 images further down the page (851 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (5)

• About 1.9 g of CO₂ per visit

  1.89 g

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

• 15 text elements with low contrast

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

  Elements (3)

• 1 form field without a label

  1 form field has no label, so screen readers announce an empty box and autofill guesses.

• No structured data

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

• 120 internal links, 29 external

  The homepage links to 120 pages on builderall.com and 29 external pages.

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

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 58 found) and read each the way a search engine does.

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

• No Content-Security-Policy

  No Content-Security-Policy header, the main browser-side defence against injected scripts.

• No clickjacking protection

  Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

• Short HSTS lifetime

  HSTS is set, but max-age is 30 days; one year is the recommended minimum.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  builderall.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

  builderall.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be builderall.com is still delivered. Reports are on, so moving to quarantine is the next step.

• SPF does not block other senders (+all)

  Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 a mx ip4:65.111.191.0/24 ip4:38.117.1.16/28 include:mail.mailingboss.net include:_spf.emfwd.name-services.com …”.

• Email authentication score: 60/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 6 trackers load before any consent

  6

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

• 10 cookies set on arrival

  10

  Opening the homepage sets 10 cookies (measured from a US location before any click).

• 18 other companies contacted

  Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.