Website review, no card needed

1st.am logo

1st.am website review

Visit site (opens in a new tab)Reviewed 12 November 202628 issues · 66 checks

This review found 28 issues worth fixing on 1st.am, 7 of them high impact, across 66 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.1 s2.2 sMay 23Nov 74.8 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.7 s
Aug 1, 20262.9 s
Aug 8, 20263.3 s
Aug 15, 20264.0 s
Aug 22, 20264.6 s
Aug 29, 20264.6 s
Sep 5, 20263.8 s
Sep 12, 20263.3 s
Sep 19, 20263.2 s
Sep 26, 20263.3 s
Oct 3, 20263.5 s
Oct 10, 20263.4 s
Oct 17, 20263.7 s
Oct 24, 20263.8 s
Oct 31, 20263.8 s
Nov 7, 20264.8 s
Real-visitor tap response (INP)75th percentile, phones
175 ms132 msMay 23Nov 7168 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026164 ms
May 30, 2026169 ms
Jun 6, 2026170 ms
Jun 13, 2026163 ms
Jun 20, 2026158 ms
Jun 27, 2026149 ms
Jul 4, 2026152 ms
Jul 11, 2026160 ms
Jul 18, 2026160 ms
Jul 25, 2026163 ms
Aug 1, 2026163 ms
Aug 8, 2026151 ms
Aug 15, 2026155 ms
Aug 22, 2026155 ms
Aug 29, 2026164 ms
Sep 5, 2026169 ms
Sep 12, 2026163 ms
Sep 19, 2026161 ms
Sep 26, 2026150 ms
Oct 3, 2026147 ms
Oct 10, 2026137 ms
Oct 17, 2026145 ms
Oct 24, 2026151 ms
Oct 31, 2026156 ms
Nov 7, 2026168 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

Full-page screenshot of 1st.am (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 1st.am at 0.4 s0.4 s
  2. 1st.am at 0.8 s0.8 s
  3. 1st.am at 1.1 s1.1 s
  4. 1st.am at 1.5 s1.5 s
  5. 1st.am at 1.9 s1.9 s
  6. 1st.am at 2.3 s2.3 s
  7. 1st.am at 2.6 s2.6 s
  8. 1st.am at 3.0 s3.0 s

Speed

2 to fix93
  • Render-blocking requests

    950 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

  • Google Tag Manager adds 437 ms

    437 ms

    Google Tag Manager costs a phone 437 ms of main-thread work and 455 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Cloudflare and JSDelivr CDN and others), adding 695 KiB and 460 ms of main-thread time.

  • Reduce unused JavaScript

    231 KiB

    About 231 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    100 ms · 102 KiB

    16 files are served with short cache lifetimes, so returning visitors download them again (102 KiB).

  • Reduce unused CSS

    150 ms · 42 KiB

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

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

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

3 checks passed
  • Mobile performance score: 93

    93/100

    Your mobile performance score is 93. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 359 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

    Your server sent the HTML in 1 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix67
  • 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 LCP: 4.6 s

    4.6 s

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

  • Real-user FCP: 4.6 s

    4.6 s

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

  • Real-user TTFB: 3.3 s

    3.3 s

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

  • Largest content (LCP) got 71% slower for real visitors

    +71%

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

  • Time to Interactive: 6.6 s

    6.6 s

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

  • Total Blocking Time: 249 ms

    249 ms

    Scripts block taps and scrolling for 249 ms in total while the page loads. Good is under 200 ms.

  • 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-11-07, real Chrome visitors' tap response (inp) went from 164 ms to 168 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user INP: 167 ms

    167 ms

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

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Speed Index: 3.2 s

    3.2 s

    Visually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.7 s

    1.7 s

    Your largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “The domain name 1st.am is for sale!”.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.22 g

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

4 checks passed
  • Page weight: 808 KiB in 28 requests

    808 KiB

    Your homepage downloads 808 KiB in 28 requests on a phone: scripts 501 KiB (7), fonts 205 KiB (3) and stylesheets 51 KiB (4). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9295
  • 5 text elements with low contrast

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

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

    All page content should be contained by landmarks: 11 elements on the page fail 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.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

9 to fixGoogle 8360
  • No meta description

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

  • Title is short (19 characters)

    Your title is only 19 characters: “1st.am is for sale!”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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 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://market.name.am/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at market.name.am/robots.txt, the first file search crawlers ask for.

  • Only 2 internal links

    The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

1 checks passed
  • One H1 headline

    Your main headline reads: “1st.am”.

AI search readiness

1 to fix69
  • 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 checks passed
  • llms.txt published

    The site publishes https://market.name.am/llms.txt (1 KiB, 4 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Best practices

1 to fixGoogle 10093
  • 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.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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 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 116 words

    The homepage has only about 116 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.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy now”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Buy a domain”, “Buy now” and “Start Negotiation”.

  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 6 other companies contacted

    Loading the homepage contacts 6 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 1st.am, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Analytics
Hosting
DigitalOcean

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on 1st.am, including 10 speed issues, 9 SEO issues and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25