bitly.com website review

About 591 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Optimizely and Optanon and others), adding 2.2 MB and 1.3 s of main-thread time.

Google Tag Manager costs a phone 697 ms of main-thread work and 845 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.

About 83 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 480 ms faster on a phone.

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

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

qrcg.net costs a phone 96 ms of main-thread work and 524 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.

qr-code-generator.com costs a phone 34 ms of main-thread work and 393 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.

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 18.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies and other analytic technologies on our websi…”.

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

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

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

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

Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Your homepage downloads 2.5 MB in 139 requests on a phone: scripts 1.7 MB (40), fonts 415 KiB (8) and images 187 KiB (33). Under 2 MB keeps phones on slow connections fast.

modal_img_landscape.webp 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 (38 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.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Structured data found (BreadcrumbList, Organization, SoftwareApplication and WebPage) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

The homepage links to 196 pages on bitly.com and 24 external pages.

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.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /pages/marketplace/shopify, whose canonical is /pages/marketplace/partner/shopify. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=355015482&Ver=2&mid=e5e4da0e-142c-4c5c-bce3-1834b401db74&bo=3&sid=fd1a63a0d86d11f1bf0149d267fad441&vid=fd1a78a0d86d11f1a45a35a94bda9ab3&vids=0&msclkid=N&pi=918639831&l.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://bitly.com' has been blocked by…”.

Chrome logged issues while loading the page (“Cookie”).

1 link to other sites is dead, for example https://uevi.co/2702RNXH (404).

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

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

2 links go through two or more redirects, for example https://facebook.com/bitly.

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.

bitly.com is registered until Nov 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.

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

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

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

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, HubSpot and Microsoft Ads and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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