26characters.com website review

website-files.com costs a phone 1.6 s of main-thread work and 2.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

7 third-party services load with your homepage (website-files.com, Google Tag Manager and cloudfront.net and others), adding 2.7 MB and 2.0 s of main-thread time.

6 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

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

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

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

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

7 KiB could be saved by minifying CSS.

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.

Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We turn B2B companies into the obvious choice.”.

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

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

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

9 images have no width and height attributes, so the layout jumps as each one loads.

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.

Your homepage downloads 2.7 MB in 65 requests on a phone: images 1.3 MB (21), scripts 1.0 MB (13) and other files 152 KiB (20). Under 2 MB keeps phones on slow connections fast.

6 images (657 KiB) 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.

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

1 image is downloaded at several times the size a phone draws it, for example 5fd295bb1c5ac2cacb23de00_26characters-white-logotype.png at 2,587 px wide, shown at 150 px. Resized copies would save about 101 KiB.

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

All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Your meta description is 174 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("www.26characters.com")”.

The homepage links to 45 pages on 26characters.com and 3 external pages.

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.

Your homepage links to /shop/shop, which answers with an error. Visitors hit a dead end and search engines drop it.

/pages/blog has no meta description, so Google writes the search snippet from whatever text it finds.

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

/project/leading-tech-risk-company and /project/top-investment-firm use the same meta description. A description written for each page earns more clicks.

/contact has 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.

/about-us, /working-with-26-characters, /technology and /risk-management took over 3 s to send their HTML from our server.

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

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 link from your homepage to your own site is broken, for example https://26characters.com/shop/shop (404).

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.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 19 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 994 words of visible text.

26characters.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

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 LinkedIn Insight (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, 1 of them by other companies (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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.