mapcorewards.com website review

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

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

5 third-party services load with your homepage (Squarespace, Google Tag Manager and sqspcdn.com and others), adding 2.7 MB and 745 ms of main-thread time.

Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.

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

12 images could be 682 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

Squarespace costs a phone 514 ms of main-thread work and 1.1 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.

sqspcdn.com costs a phone 72 ms of main-thread work and 405 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.

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

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

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

1 file is served with short cache lifetimes, so returning visitors download them again (8 KiB).

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 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

Scripts block taps and scrolling for 290 ms in total while the page loads. Good is under 200 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 106 ms to 96 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 3.2 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.9 MB in 99 requests on a phone: scripts 1.5 MB (56), images 1.0 MB (18) and stylesheets 174 KiB (15). Under 2 MB keeps phones on slow connections fast.

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

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

Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/6564d8b916f3431c6a5…”.

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 58 pages on mapcorewards.com and 25 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.mapcorewards.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.mapcorewards.com/store-locator, https://www.mapcorewards.com/careers, https://www.mapcorewards.com/my-reward, https://www.mapcorewards.com/fundraise-with-mapco, https://www.mapcorewards.com/mapco-fleet and https://www.mapcorewards.com/nobleromans and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mapcorewards.com/store-locator, https://www.mapcorewards.com/careers, https://www.mapcorewards.com/my-reward, https://www.mapcorewards.com/fundraise-with-mapco, https://www.mapcorewards.com/mapco-fleet and https://www.mapcorewards.com/nobleromans and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mapcorewards.com/store-locator, https://www.mapcorewards.com/my-reward, https://www.mapcorewards.com/mapco-fleet, https://www.mapcorewards.com/nobleromans, https://www.mapcorewards.com/mobile-app and https://www.mapcorewards.com/promos-store/p/2300-points-25-off-per-gal and 5 others have 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.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/6564d8b916f3431c6a541a80/52/5c5a…”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 275 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 5 cookies (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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.