parcelsapp.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user INP: 266 ms

  266 ms

  Real visitors wait 266 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

• Tap response (INP) got 25% slower for real visitors

  +25%

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

• Real-user TTFB: 926 ms

  926 ms

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

• Largest content (LCP) held steady for real visitors

  +6%

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

• Page weight: 2.1 MB

  2.1 MB

  Your homepage downloads 2.1 MB on a phone, 43 KiB of it images (2%). Under 2 MB keeps phones on slow connections fast.

• About 0.6 g of CO₂ per visit

  0.59 g

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

• 1 button without a name

  1 button has no accessible name, so screen readers announce just “button”.

  Elements (1)

• 43 text elements with low contrast

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

  Elements (3)

• 7 images without alt text

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

  View sourceElements (3)

• 152 links without text

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

  Elements (3)

• All page content should be contained by landmarks (44 elements)

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

  Elements (3)

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

• 4 form fields without a label

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

  View sourceElements (1)

• Headings skip levels

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

  View source

• No structured data

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

• No XML sitemap

  No XML sitemap at https://parcelsapp.com/sitemap.xml.gz, so Google discovers your pages only by following links.

• No X (Twitter) card tag

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

• 270 internal links, 3 external

  The homepage links to 270 pages on parcelsapp.com and 3 external pages.

• No Organization structured data

  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.

• 1 page points its canonical at the homepage

  https://parcelsapp.com/en declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  Elements (1)

• 1 linked page hidden from search

  https://parcelsapp.com/developers/console is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  Elements (1)

• 2 pages share a title

  / and https://parcelsapp.com/en all use the title “Universal Parcel Tracking - Global Package Tracking”. Search engines can't tell which page to show for a search, so each competes with the others.

  Elements (2)

• 1 page without a meta description

  https://parcelsapp.com/developers/console has no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (1)

• 1 page without an H1

  https://parcelsapp.com/developers/console has no <h1> headline, so visitors and search engines get no clear main topic.

• 1 page with very little text

  https://parcelsapp.com/developers/docs 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.

• 15 internal pages checked

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

• 4 JavaScript errors while loading

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

• No call to action on the first screen

  On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

• About 263 words of copy

  The homepage carries about 263 words of visible text.

• 8 trackers load before any consent

  8

  Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 3 mores (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.

• 10 cookies set on arrival

  10

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

• No consent tool detected

  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.

• 85 other companies contacted

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