borderless.world website review

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

Your mobile performance score is 69 (desktop: 90). Pages that score under 90 lose visitors before the first paint.

About 171 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

About 26 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.

7 third-party services load with your homepage (Google Tag Manager, Clarity and posthog.com and others), adding 264 KiB and 234 ms of main-thread time.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Oops! Something went wrong.”.

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

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

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

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

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

2 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.

2 images (2.5 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.

mobilebg.32fbba4c.svg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example image at 2,675 px wide, shown at 110 px. Resized copies would save about 62 KiB.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

A phone browser shows 924 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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.

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.

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

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

http://borderless.world does not redirect to https, so some visitors land on the insecure version.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

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

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

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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

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

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

borderless.world is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

borderless.world 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.

borderless.world'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.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 924 words of visible text.

DMARC is set to p=none, so mail pretending to be borderless.world is still delivered. Add a report address, check the reports, then move to quarantine.

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.

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

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

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.

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