intermiamicf.com website review

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

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

25 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.0 s faster on a phone.

tiktokcdn-us.com costs a phone 1.0 s of main-thread work and 74.5 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.

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

609 KiB could be saved by minifying JavaScript.

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

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

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

Google Tag Manager costs a phone 1.2 s of main-thread work and 1.3 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 25. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, tiktokcdn-us.com and gofevo.com and others), adding 85.1 MB and 4.4 s of main-thread time.

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

gofevo.com costs a phone 662 ms of main-thread work and 5.9 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 419 ms of main-thread work and 609 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.

Google Maps costs a phone 291 ms of main-thread work and 786 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.

30 KiB could be saved by minifying CSS.

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

Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need.

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.44 (75th percentile). Good is under 0.1.

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

Your largest element takes 75.6 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 45.1 s (Speed Index). Good is under 3.4 s.

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

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

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

Real visitors wait 233 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-24, real Chrome visitors' tap response (inp) went from 145 ms to 181 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

9 images 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' largest content (lcp) went from 2.7 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 96.0 MB in 724 requests on a phone: media 66.1 MB (14), scripts 15.0 MB (249) and images 11.0 MB (147). Under 2 MB keeps phones on slow connections fast.

9 images (827 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 are downloaded at several times the size a phone draws them, for example IMCF_Logos-01_qxhjrp.png at 3,300 px wide, shown at 38 px. Resized copies would save about 465 KiB.

7 images further down the page (378 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 27.21 g of CO₂e: 3265.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

3 frames have no title, so screen-reader users cannot tell what they contain.

[role]s are not contained by their required parent element (41 elements).

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

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.

Alternative text of images should not be repeated as text: 29 elements on the page fail this check, rated minor by axe-core.

6 visible links have no text or label, so screen readers cannot say where they go.

Elements with visible text labels do not have matching accessible names. (1 element).

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

Your title is only 14 characters: “Inter Miami CF”. 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.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 116 pages on intermiamicf.com and 70 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.intermiamicf.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.intermiamicf.com/nu-stadium/index, https://www.intermiamicf.com/community/foundation, https://www.intermiamicf.com/team-store, https://www.intermiamicf.com/news/index and https://www.intermiamicf.com/video/latest/index and 3 others all use the title “Inter Miami CF”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.intermiamicf.com/nu-stadium/index, https://www.intermiamicf.com/community/foundation, https://www.intermiamicf.com/team-store, https://www.intermiamicf.com/news/index, https://www.intermiamicf.com/video/latest/index and https://www.intermiamicf.com/community/index and 2 others use the same meta description. A description written for each page earns more clicks.

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

https://www.intermiamicf.com/team-store and https://www.intermiamicf.com/events/index have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.intermiamicf.com/tickets/member-central/index, https://www.intermiamicf.com/news/index and https://www.intermiamicf.com/video/latest/index took over 3 s to send their HTML from our server.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

6 errors were logged to the browser console while the page loaded, for example “ErrorUtils caught an error: Cannot read properties of undefined (reading 'id') Subsequent non-fatal errors won't be log…”.

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

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 779 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 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 11 cookies, 1 of them by other companies (measured from a US location before any click).

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