Website review, no card needed
facebookcareers.com website review
Visit site (opens in a new tab)Reviewed 20 November 202627 issues · 62 checks
This review found 27 issues worth fixing on facebookcareers.com, 11 of them high impact, across 62 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.5 s |
| Jun 6, 2026 | 4.7 s |
| Jun 13, 2026 | 4.8 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 4.7 s |
| Jul 4, 2026 | 4.8 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 4.8 s |
| Jul 25, 2026 | 4.8 s |
| Aug 1, 2026 | 4.7 s |
| Aug 8, 2026 | 4.6 s |
| Aug 15, 2026 | 4.4 s |
| Aug 22, 2026 | 4.3 s |
| Aug 29, 2026 | 4.2 s |
| Sep 5, 2026 | 4.2 s |
| Sep 12, 2026 | 4.2 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 4.1 s |
| Oct 24, 2026 | 4.2 s |
| Oct 31, 2026 | 4.2 s |
| Nov 7, 2026 | 4.2 s |
| Nov 14, 2026 | 4.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 271 ms |
| Jun 6, 2026 | 267 ms |
| Jun 13, 2026 | 262 ms |
| Jun 20, 2026 | 261 ms |
| Jun 27, 2026 | 254 ms |
| Jul 4, 2026 | 250 ms |
| Jul 11, 2026 | 245 ms |
| Jul 18, 2026 | 244 ms |
| Jul 25, 2026 | 238 ms |
| Aug 1, 2026 | 236 ms |
| Aug 8, 2026 | 231 ms |
| Aug 15, 2026 | 228 ms |
| Aug 22, 2026 | 235 ms |
| Aug 29, 2026 | 233 ms |
| Sep 5, 2026 | 234 ms |
| Sep 12, 2026 | 235 ms |
| Sep 19, 2026 | 227 ms |
| Sep 26, 2026 | 226 ms |
| Oct 3, 2026 | 225 ms |
| Oct 10, 2026 | 228 ms |
| Oct 17, 2026 | 230 ms |
| Oct 24, 2026 | 231 ms |
| Oct 31, 2026 | 231 ms |
| Nov 7, 2026 | 228 ms |
| Nov 14, 2026 | 225 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
Not measured in this review.
Core Web Vitals
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 LCP: 4.1 s
4.1 sReal visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.7 s
3.7 sReal visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.
Real-user INP: 223 ms
223 msReal visitors wait 223 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
3 checks passed
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Tap response (INP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 271 ms to 225 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.5 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.3 MB
5.3 MBYour homepage downloads 5.3 MB on a phone, 2.4 MB of it images (45%). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
media weighs 1.7 MB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
1.6 MB2 images are downloaded at several times the size a phone draws them, for example media at 2,880 px wide, shown at 342 px. Resized copies would save about 1.6 MB.
An image on the first screen is lazy-loaded
media is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
6 images below the first screen load straight away
6 images further down the page (278 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.49 g of CO₂e: 178.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
ARIA commands must have an accessible name (1 element)
ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
autocomplete attribute must be used correctly (1 element)
autocomplete attribute must be used correctly: 1 element on the page fails this check, rated serious by axe-core.
Users should be able to zoom and scale the text up to 500% (1 element)
Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 120 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 H1 headlines
There are 4 <h1> headlines (“Put your skills to work as we build for the futur…”, “Introducing Muse: Your personal AI agent” and “Introducing Muse: Your personal AI agent”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (Event, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://www.meta.com)”.
No XML sitemap
No XML sitemap at https://www.metacareers.com/sitemap/www_metacareers_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.
16 internal links, 46 external
The homepage links to 16 pages on facebookcareers.com and 46 external pages.
5 checks passed
Meta description: 125 characters
Your meta description is 125 characters: “Meta's mission is to build the future of human connection and the technology that makes it possible. Find your job with…”.
Title: 64 characters
Your title is a healthy 64 characters: “Meta Jobs & Careers | Do the Most Meaningful Work of Your Career”.
Canonical URL set
The canonical URL is https://www.metacareers.com/.
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 and points crawlers to your sitemap.
AI search readiness
No llms.txt
There is no https://www.metacareers.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.
3 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,307 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.metacareers.com/podcasts 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.
2 pages share a title
https://www.metacareers.com/jobsearch and https://www.metacareers.com/podcasts all use the title “Meta Careers”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.metacareers.com/podcasts and https://www.metacareers.com/phishing-scam have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://www.metacareers.com/jobsearch, https://www.metacareers.com/blog, https://www.metacareers.com/podcasts, https://www.metacareers.com/teams/technology/ai, https://www.metacareers.com/teams/technology/metaverse-and-wearables and https://www.metacareers.com/teams/technology/infrastructure and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 8 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.”.
2 checks passed
Tap targets are thumb-sized
7 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 935 words of copy
The homepage carries about 935 words of visible text.
1 checks passed
39 calls to action
The homepage has 39 calls to action, for example “Try Muse”, “Learn more” and “Learn more about Meta Model API”.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
5 other companies contacted
Loading the homepage contacts 5 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 facebookcareers.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Facebook, Inc.
Company
- Headquarters
- Menlo Park
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on facebookcareers.com, including 5 speed issues, 3 SEO issues and 6 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.