1stratelistings.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 LCP: 3.4 s

  3.4 s

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

• Real-user INP: 253 ms

  253 ms

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

• Real-user FCP: 2.0 s

  2.0 s

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

• Real-user TTFB: 838 ms

  838 ms

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

• Tap response (INP) held steady for real visitors

  -4%

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

• Largest content (LCP) held steady for real visitors

  +3%

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

• About 0.2 g of CO₂ per visit

  0.24 g

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

• Required ARIA attributes must be provided (1 element)

  Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• Frames without titles

  1 frame has no title, so screen-reader users cannot tell what it contains.

  Elements (1)

• <html> element must have a lang attribute (1 element)

  <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• Zoom is disabled

  The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  Elements (1)

• All page content should be contained by landmarks (1 element)

  All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• ARIA role should be appropriate for the element (1 element)

  ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  Elements (1)

• Headings should not be empty (1 element)

  Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  Elements (1)

• robots.txt blocks all crawlers

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

• No meta description

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

• No H1 headline

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

• Title is short (8 characters)

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

  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 social preview image

  No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

• No XML sitemap

  No XML sitemap at https://www.facebook.com/sitemap/groups_gp_i18n_titles_1_posts_0.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 incomplete here.

• 18 internal links, 10 external

  The homepage links to 18 pages on 1stratelistings.com and 10 external pages.

• robots.txt blocks 6 AI answer engine crawlers

  6 of 6

  Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

• 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.

• No llms.txt

  There is no https://www.facebook.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.

• Opted out of AI training for 5 crawlers

  robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

• 3 pages share a title

  https://www.facebook.com/login?next=https%3A%2F%2Fwww.facebook.com%2F1stratelistings, https://www.facebook.com/recover/initiate and https://www.facebook.com/privacy/center all use the title “Facebook”. Search engines can't tell which page to show for a search, so each competes with the others.

  Elements (3)

• 2 pages without a meta description

  https://www.facebook.com/recover/initiate and https://www.facebook.com/privacy/center have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (2)

• 1 link to non-canonical URLs

  Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.facebook.com/policies/cookies, whose canonical is https://www.facebook.com/privacy/policies/cookies?entry_point=cookie_policy_redirect&entry=0. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  Elements (1)

• 7 pages without an H1

  https://www.facebook.com/recover/initiate, https://www.facebook.com/lite, https://www.facebook.com/watch, https://www.facebook.com/privacy/policy, https://www.facebook.com/privacy/center and https://www.facebook.com/about and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

• 2 pages with very little text

  https://www.facebook.com/recover/initiate and https://www.facebook.com/policies 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.

• 1 page slow to respond

  https://www.facebook.com/about took over 3 s to send its HTML from our server.

• 15 internal pages checked

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

• No mobile viewport

  No viewport meta tag, so phones render the desktop layout zoomed out.

• 2 small tap targets

  2 of 5 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getElementsByTagName')”.

• 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.

• 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.

• Only about 25 words

  The homepage has only about 25 words of visible text; thin pages give Google and first-time buyers little to go on.

• 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.

• 2 trackers load before any consent

  2

  Before a visitor clicks anything, the page loads Google Ads 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

  5

  Opening 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.

• 9 other companies contacted

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