timbers.com website review

208 files are served with short cache lifetimes, so returning visitors download them again (5.3 MB).

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

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

609 KiB could be saved by minifying JavaScript.

11 images could be 739 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.

416 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 2.4 s faster on a phone.

About 333 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and gofevo.com and others), adding 6.5 MB and 2.3 s of main-thread time.

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

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

gofevo.com costs a phone 273 ms of main-thread work and 3.0 MB 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.

Google/Doubleclick Ads costs a phone 483 ms of main-thread work and 852 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.

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

30 KiB could be saved by minifying CSS.

Other Google APIs/SDKs costs a phone 233 ms of main-thread work and 948 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.

cookiepro.com costs a phone 251 ms of main-thread work and 249 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.

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.

For real visitors the layout shifts by 0.39 (75th percentile). Good is under 0.1.

Your largest element takes 40.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our partners use cookies, pixels, and similar tracki…”.

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

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

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

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

The layout shifts by 0.532 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.7 MB in 447 requests on a phone: scripts 8.0 MB (123), images 1.7 MB (105) and other files 888 KiB (173). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example tzkiifqssndu3lxmjncc at 824 px wide, shown at 120 px. Resized copies would save about 49 KiB.

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

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

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

Certain ARIA roles must be contained by particular parents: 40 elements on the page fail this check, rated critical by axe-core.

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

[role="img"] and [role="image"] elements must have alternative text: 12 elements on the page fail this check, rated serious by axe-core.

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.

Elements with visible text labels do not have matching accessible names. (6 elements).

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

Your title is only 16 characters: “Portland Timbers”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 77 pages on timbers.com and 71 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 https://www.timbers.com/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.

/, https://www.timbers.com/tickets/index, https://www.timbers.com/schedule, https://www.timbers.com/roster, https://www.timbers.com/news/latest/index and https://www.timbers.com/video/latest/index and 6 others all use the title “Portland Timbers”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.timbers.com/tickets/index, https://www.timbers.com/schedule, https://www.timbers.com/roster, https://www.timbers.com/news/latest/index, https://www.timbers.com/video/latest/index and https://www.timbers.com/providencepark/index and 5 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://www.timbers.com/tickets/index, whose canonical is https://www.timbers.com/tickets. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.timbers.com/t2/index and https://www.timbers.com/video/highlights-st-louis-city-sc-vs-portland-timbers-oct-28-2026 have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.timbers.com/camps/index, https://www.timbers.com/albums/index, https://www.timbers.com/academy/index and https://www.timbers.com/t2/index took over 3 s to send their HTML from our server.

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

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

3 errors were logged to the browser console while the page loaded, for example “AlpineModules is not defined”.

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

Social proof on the homepage: 6 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,104 words of visible text.

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

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 11 cookies, 1 of them by other companies (measured from a US location before any click).

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