logos.com website review

The page goes through 1 redirect before it starts loading, costing about 10.1 s. Link and advertise the final URL directly.

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.3 s faster on a phone.

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

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

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

faithlifecdn.com costs a phone 0 ms of main-thread work and 737 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.

4 third-party services load with your homepage (Optimizely, Google Fonts and logoscdn.com and others), adding 979 KiB and 103 ms of main-thread time.

About 136 KiB of CSS is downloaded but never applied on this page.

Desktop scores 54 but mobile only 28. A gap that wide usually means heavy scripts and images that hit phones hardest.

3 KiB could be saved by minifying CSS.

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.3 s (75th percentile). Good is under 1.8 s.

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

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

Your largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

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

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

Your homepage downloads 8.4 MB in 210 requests on a phone: scripts 5.7 MB (90), images 1.4 MB (39) and HTML 623 KiB (5). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example optimized at 1,408 px wide, shown at 342 px. Resized copies would save about 44 KiB.

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

2 buttons have no accessible name, so screen readers announce just “button”.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

18 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 21 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.

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Headings skip levels (h3 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

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

Google's crawler is blocked from indexing this page.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 546 pages on logos.com and 62 external pages.

Your homepage links to https://www.logos.com/culture/en-US, https://www.logos.com/culture/es-US, https://www.logos.com/culture/en-CA, https://www.logos.com/culture/fr-CA, https://www.logos.com/culture/en-GB and https://www.logos.com/culture/en-AU and 9 others, which answer with an error. Visitors hit a dead end and search engines drop them.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5439780&tm=gtm002&Ver=2&mid=e7f2bf8b-09c2-452e-a9d8-8af0e8cc7bef&bo=1&sid=06ef1030d28e11f1bd97ebec3317ab16&vid=06ef0c60d28e11f196a97972263ccf0f&vids=1&msclkid=N&pi=918.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 608 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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

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

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