Website review, no card needed

techsposanfrancisco.com logo

techsposanfrancisco.com website review

Visit site (opens in a new tab)Reviewed 9 November 202617 issues · 59 checks

This review found 17 issues worth fixing on techsposanfrancisco.com, 4 of them high impact, across 59 checks. The most urgent: <html> element must have a lang attribute (1 element). 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
6.9 s4.7 sMay 23Aug 154.9 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20266.1 s
May 30, 20266.3 s
Jun 6, 20266.4 s
Jun 13, 20266.5 s
Jun 20, 20266.6 s
Jun 27, 20266.7 s
Jul 4, 20266.7 s
Jul 11, 20266.7 s
Jul 18, 20266.6 s
Aug 1, 20265.1 s
Aug 8, 20265.1 s
Aug 15, 20264.9 s
Real-visitor tap response (INP)75th percentile, phones
825 ms672 msMay 23Jul 18690 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026778 ms
May 30, 2026790 ms
Jun 6, 2026802 ms
Jun 13, 2026803 ms
Jun 20, 2026807 ms
Jun 27, 2026795 ms
Jul 4, 2026775 ms
Jul 11, 2026771 ms
Jul 18, 2026690 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 techsposanfrancisco.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

100
  • Document request latency

    2 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

3 checks passed
  • Mobile performance score: 100

    100/100

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

  • Main-thread work: 0.0 s

    A phone's processor spends 0.0 s on main-thread work while loading, 4 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

100
  • Tap response (INP) held steady for real visitors

    -7%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

7 checks passed
  • Largest content (LCP) got 19% faster for real visitors

    -19%

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

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.8 s

    0.8 s

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

  • Largest Contentful Paint: 0.8 s

    0.8 s

    Your largest element renders in 0.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Error establishing a database connection”.

  • Speed Index: 1.0 s

    1.0 s

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

  • Time to Interactive: 0.8 s

    0.8 s

    The page is fully interactive after 0.8 s.

Images and page weight

100
  • About 0.00 g of CO₂ per visit

    0.00 g

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

1 checks passed
  • Page weight: 3 KiB in 1 request

    3 KiB

    Your homepage downloads 3 KiB in 1 request on a phone: HTML 3 KiB (1). That is a lean page.

Accessibility

4 to fixGoogle 7977
  • <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.

  • 7 images without alt text

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

  • No main landmark

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

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

  • Headings skip levels

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

1 checks passed
  • 9 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 12 WCAG 2.2 A/AA and best-practice rules on the phone render: 9 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 7362
  • Error status code

    The page answers with an error status, so search engines may drop it.

  • Title is short (26 characters)

    Your title is only 26 characters: “TECHSPO San Francisco 2026”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (363 characters)

    Your meta description is 363 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 3 problems

    Structured data found ((untyped), BreadcrumbList, BusinessEvent and Organization) but with 3 problems, for example “Organization: url points at a different host (https://techsposv.com)”.

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at techsposanfrancisco.com/robots.txt, the first file search crawlers ask for.

  • No favicon declared

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

  • 113 internal links, 138 external

    The homepage links to 113 pages on techsposanfrancisco.com and 138 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “Choose your own experience”.

  • Canonical URL set

    The canonical URL is https://techsposanfrancisco.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

100
  • No llms.txt

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

1 checks passed
  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

Other pages

1 to fix95
  • 1 page without a meta description

    https://techsposanfrancisco.com/networking-opportunities has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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.

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

  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 5 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • 25 calls to action

    The homepage has 25 calls to action, for example “BUY TICKETS”, “Book an Exhibit Booth” and “Request an Exhibitor Prospectus”.

  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 techsposanfrancisco.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
InMotion Hosting, Inc.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 17 issues on techsposanfrancisco.com, including 7 SEO issues and 4 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