Website review, no card needed

any.company logo

any.company website review

Visit site (opens in a new tab)Reviewed 23 October 202628 issues · 64 checks

This review found 28 issues worth fixing on any.company, 9 of them high impact, across 64 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of any.company (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. any.company at 0.8 s0.8 s
  2. any.company at 1.6 s1.6 s
  3. any.company at 2.4 s2.4 s
  4. any.company at 3.2 s3.2 s
  5. any.company at 4.0 s4.0 s
  6. any.company at 4.8 s4.8 s
  7. any.company at 5.6 s5.6 s
  8. any.company at 6.3 s6.3 s

Speed

6 to fix63
  • Use efficient cache lifetimes

    2.5 s · 537 KiB

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

  • Render-blocking requests

    1.8 s

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

  • Improve image delivery

    1.0 s · 140 KiB

    1 image could be 140 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63 (desktop: 94). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    310 ms · 93 KiB

    About 93 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.

  • Minify JavaScript

    310 ms · 87 KiB

    87 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    150 ms · 33 KiB

    About 33 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.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google CDN and JSDelivr CDN), adding 44 KiB and 23 ms of main-thread time.

  • Minify CSS

    11 KiB

    11 KiB could be saved by minifying CSS.

  • Phones get a much slower page than desktops

    Desktop scores 94 but mobile only 63. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 0.7 s

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

4 to fix55
  • Cumulative Layout Shift: 0.415

    0.415

    The layout shifts by 0.415 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest Contentful Paint: 4.3 s

    4.3 s

    Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Any.Company app features: share your location and topics, j…”.

  • First Contentful Paint: 2.3 s

    2.3 s

    The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 4.3 s

    4.3 s

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

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

2 checks passed
  • Speed Index: 3.4 s

    3.4 s

    Visually, the page fills in at 3.4 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.

Images and page weight

4 to fix58
  • 1 image over 500 KB

    68e9306c54e6002385c1029a_opengraph.jpg weighs 566 KiB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    68e9306c54e6002385c1029a_opengraph.jpg 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).

  • 2 images in older formats

    2 images (632 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.

  • 1 image far larger than shown

    348 KiB

    1 image is downloaded at several times the size a phone draws it, for example 68e9306c54e6002385c1029a_opengraph.jpg at 1,200 px wide, shown at 248 px. Resized copies would save about 348 KiB.

  • About 0.2 g of CO₂ per visit

    0.17 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.17 g of CO₂e: 19.9 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: 600 KiB in 31 requests

    600 KiB

    Your homepage downloads 600 KiB in 31 requests on a phone: scripts 328 KiB (17), images 189 KiB (4) and stylesheets 64 KiB (5). That is a lean page.

Accessibility

1 to fixGoogle 9698
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

5 to fixGoogle 9274
  • No H1 headline

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

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

  • No robots.txt

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

  • 15 internal links, 3 external

    The homepage links to 15 pages on any.company and 3 external pages.

3 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Share your availability to meet or travel for events, travel groups, neighbours, businesses and organisations. On Googl…”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Any.Company - Share your availability to meet or travel”.

  • Open Graph tags complete

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

AI search readiness

1 to fix81
  • 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://any.company/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
  • Text is in the HTML

    Your server sends the page's text in the HTML (525 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 4 linked pages hidden from search

    https://any.company/meet-and-chat, https://any.company/events, https://any.company/b2b and https://any.company/ConsentOverview are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 7 pages without a meta description

    https://any.company/meet-and-chat, https://any.company/b2b, https://any.company/PrivacyPolicy, https://any.company/CookiePolicy, https://any.company/UserAgreement and https://any.company/CommunityStandards and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://any.company/meet-and-chat, https://any.company/events, https://any.company/app, https://any.company/b2b, https://any.company/PrivacyPolicy and https://any.company/CookiePolicy and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://any.company/newsletter, https://any.company/PrivacyPolicy, https://any.company/CookiePolicy, https://any.company/UserAgreement and https://any.company/CommunityStandards 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.

  • 13 internal pages checked

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

4 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

  • 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 a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 15 small tap targets

    15 of 40 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 fix60
  • 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.

  • 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 619 words of copy

    The homepage carries about 619 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Meetup events find something to join” and “Learn More”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Meetup eventsfind something to join”, “DOWNLOAD ON THEApp Store” and “Schedule a free demo”.

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.

  • 3 other companies contacted

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

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 any.company, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery

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 any.company, including 10 speed issues, 5 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