Website review, no card needed
amazon.jobs website review
Visit site (opens in a new tab)Reviewed 12 October 202647 issues · 86 checks
This review found 47 issues worth fixing on amazon.jobs, 15 of them high impact, across 86 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 2.3 s |
| Apr 25, 2026 | 2.3 s |
| May 2, 2026 | 2.3 s |
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 212 ms |
| Apr 25, 2026 | 210 ms |
| May 2, 2026 | 208 ms |
| May 9, 2026 | 207 ms |
| May 16, 2026 | 208 ms |
| May 23, 2026 | 211 ms |
| May 30, 2026 | 213 ms |
| Jun 6, 2026 | 216 ms |
| Jun 13, 2026 | 217 ms |
| Jun 20, 2026 | 217 ms |
| Jun 27, 2026 | 216 ms |
| Jul 4, 2026 | 218 ms |
| Jul 11, 2026 | 218 ms |
| Jul 18, 2026 | 218 ms |
| Jul 25, 2026 | 217 ms |
| Aug 1, 2026 | 216 ms |
| Aug 8, 2026 | 217 ms |
| Aug 15, 2026 | 217 ms |
| Aug 22, 2026 | 216 ms |
| Aug 29, 2026 | 212 ms |
| Sep 5, 2026 | 209 ms |
| Sep 12, 2026 | 207 ms |
| Sep 19, 2026 | 206 ms |
| Sep 26, 2026 | 205 ms |
| Oct 3, 2026 | 204 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Render-blocking requests
4.5 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.5 s.
Reduce unused JavaScript
1.2 s · 2.1 MBAbout 2.1 MB 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.
Mobile performance score: 34
34/100Your mobile performance score is 34 (desktop: 26). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (amazon.dev, Google Tag Manager and cloudfront.net and others), adding 3.2 MB and 1.6 s of main-thread time.
amazon.dev adds 794 ms
794 msamazon.dev costs a phone 794 ms of main-thread work and 2.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.
Use efficient cache lifetimes
300 ms · 620 KiB20 files are served with short cache lifetimes, so returning visitors download them again (620 KiB).
Google Tag Manager adds 665 ms
665 msGoogle Tag Manager costs a phone 665 ms of main-thread work and 938 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 721 ms. During a long task the page ignores taps.
Reduce unused CSS
450 ms · 68 KiBAbout 68 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Legacy JavaScript
300 ms · 40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
224 KiB5 images could be 224 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user CLS: 1.04
1.04For real visitors the layout shifts by 1.04 (75th percentile). Good is under 0.1.
Real-user FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 29.7 s
29.7 sThe page becomes fully interactive after 29.7 s. Good is under 3.8 s.
First Contentful Paint: 6.7 s
6.7 sThe first text or image appears after 6.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 7.9 s
7.9 sYour largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Amazon Jobs uses cookies and similar tools such as pixels (…”.
Speed Index: 11.0 s
11.0 sVisually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 986 ms
986 msScripts block taps and scrolling for 986 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 212 ms to 204 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 186 ms
186 msReal visitors wait 186 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0.067
0.067The layout barely moves while loading (CLS 0.067, good is under 0.1).
Images and page weight
Page weight: 4.8 MB in 93 requests
4.8 MBYour homepage downloads 4.8 MB in 93 requests on a phone: scripts 3.7 MB (20), images 574 KiB (30) and fonts 343 KiB (9). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (651 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.
4 images below the first screen load straight away
4 images further down the page (416 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
21 KiB1 image is downloaded at several times the size a phone draws it, for example Xiaole_Small.jpg at 543 px wide, shown at 165 px. Resized copies would save about 21 KiB.
About 1.4 g of CO₂ per visit
1.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.35 g of CO₂e: 162.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Positive tabindex
6 elements have a tabindex above 0, which scrambles the keyboard order.
All page content should be contained by landmarks (27 elements)
All page content should be contained by landmarks: 27 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
2 checks passed
Every image has alt text
All 2 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://amazon.jobs/sitemap.xml, so Google discovers your pages only by following links.
32 internal links, 8 external
The homepage links to 32 pages on amazon.jobs and 8 external pages.
5 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “Explore corporate jobs and career programs at Amazon, from full-time roles to internships. Join our global teams and cr…”.
One H1 headline
Your main headline reads: “Impact the future, today”.
Title: 40 characters
Your title is a healthy 40 characters: “Amazon Careers: Impact the Future, Today”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
AI search readiness
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.
Some text only appears after JavaScript runs
34%The HTML your server sends has 185 of the 546 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://amazon.jobs/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.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
8 pages share 4 titles
https://amazon.jobs/en/business_categories and https://amazon.jobs/content/en/teams all use the title “Teams”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://amazon.jobs/en/business_categories, https://amazon.jobs/en/job_categories, https://amazon.jobs/user/details, https://amazon.jobs/applicant/communication-preferences, https://amazon.jobs/content/faq and https://amazon.jobs/content/en/job-categories and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://amazon.jobs/content/our-workplace/working-at-amazon and https://amazon.jobs/content/en/our-workplace use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://amazon.jobs/user/details and https://amazon.jobs/applicant/communication-preferences have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://amazon.jobs/en/locations, https://amazon.jobs/en/job_categories and https://amazon.jobs/applicant/communication-preferences took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 28 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://bat.bing.com/bat.js' violates the following Content Security Policy directive: "script-src-…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 546 words of copy
The homepage carries about 546 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Apply now” and “Download Amazon A to Z app”.
6 calls to action
The homepage has 6 calls to action, for example “Join us on facebook”, “Join us on linkedin” and “Join us on instagram”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight (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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
23 other companies contacted
Loading the homepage contacts 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at amazon.jobs, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on amazon.jobs, including 22 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.