myewards.com website review

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

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

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

JSDelivr CDN costs a phone 1.1 s of main-thread work and 440 KiB 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.

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

8 third-party services load with your homepage (JSDelivr CDN, Google Tag Manager and Facebook and others), adding 928 KiB and 1.5 s of main-thread time.

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

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

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

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

17 KiB could be saved by minifying CSS.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

7 KiB could be saved by minifying JavaScript.

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 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “CRM software that enhances personalization, customer engage…”.

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

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

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

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

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

72 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-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.6 MB in 58 requests on a phone: images 10.4 MB (25), scripts 585 KiB (14) and fonts 265 KiB (2). Under 2 MB keeps phones on slow connections fast.

5 images weigh 9.2 MB together. On a phone connection a single image that size takes seconds.

13 images are downloaded at several times the size a phone draws them, for example website-final+pngs-02.png at 2,917 px wide, shown at 198 px. Resized copies would save about 8.1 MB.

16 images (9.9 MB) 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 (8.2 MB) 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.27 g of CO₂e: 392.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), 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 31 pages on myewards.com and 10 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://myewards.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://myewards.com/privacy-policy and https://myewards.com/disclaimer use the same meta description. A description written for each page earns more clicks.

https://myewards.com/posdashboard, https://myewards.com/privacy-policy and https://myewards.com/disclaimer have no <h1> headline, so visitors and search engines get no clear main topic.

https://myewards.com/posdashboard 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.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

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

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

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

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