Website review, no card needed

luby.co logo

luby.co website review

Visit site (opens in a new tab)Reviewed 18 November 202618 issues · 72 checks

This review found 18 issues worth fixing on luby.co, 5 of them high impact, across 72 checks. The most urgent: page weight: 20.4 MB in 101 requests. 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 luby.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix83
  • Use efficient cache lifetimes

    7.8 MB

    31 files are served with short cache lifetimes, so returning visitors download them again (7.8 MB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and openai.com and others), adding 952 KiB and 963 ms of main-thread time.

  • Mobile performance score: 83

    83/100

    Your mobile performance score is 83. Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 632 ms

    632 ms

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

  • 11 long tasks on the main thread

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

  • Reduce unused JavaScript

    316 KiB

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

  • Main-thread work: 2.7 s

    A phone's processor spends 2.7 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 1,558 HTML elements

    The page has 1,558 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    127 KiB

    4 images could be 127 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    25 KiB

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

  • Reduce unused CSS

    15 KiB

    About 15 KiB of CSS is downloaded but never applied on this page.

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

1 checks passed
  • Server response: 42 ms

    42 ms

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

Core Web Vitals

3 to fix85
  • Time to Interactive: 13.2 s

    13.2 s

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

  • Total Blocking Time: 532 ms

    532 ms

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

  • Speed Index: 4.6 s

    4.6 s

    Visually, the page fills in at 4.6 s (Speed Index). Good is under 3.4 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.

3 checks passed
  • 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 “When nobody knows exactly what the system does, every chang…”.

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix70
  • Page weight: 20.4 MB in 101 requests

    20.4 MB

    Your homepage downloads 20.4 MB in 101 requests on a phone: media 18.5 MB (3), scripts 1.2 MB (31) and images 441 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • About 5.8 g of CO₂ per visit

    5.77 g

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

3 checks passed
  • 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 9495
  • 15 text elements with low contrast

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

  • Interactive controls must not be nested (5 elements)

    Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (5 elements).

2 checks passed
  • Every image has alt text

    All 108 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

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

SEO

Google 100100
  • 113 internal links, 11 external

    The homepage links to 113 pages on luby.co and 11 external pages.

8 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “AI-first software development in Miami and São Paulo, founded in 2002. Luby Software helps you ship faster without risk…”.

  • One H1 headline

    Your main headline reads: “Luby Software · AI-first engineering · Founded 2002 · Miami & São Paulo”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “AI-First Software Development, Founded 2002 | Luby Software”.

  • Canonical URL set

    The canonical URL is https://luby.co/.

  • Structured data in place

    Structured data found: FAQPage, Organization and WebSite.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://luby.co/sitemap.xml.

AI search readiness

100
4 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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://luby.co/llms.txt (11 KiB, 71 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    17 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 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 2,304 words of copy

    The homepage carries about 2,304 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Talk to a specialist”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Pricing”, “Contact” and “Schedule a meeting”.

  • 1 short form

    A short form (6 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 32 testimonial or review blocks, 60 customer or partner logos, a star rating, 8 trust badges and “540+ clients”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies, 6 of them by other companies (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.

  • 17 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
Next.js
Analytics
Google Tag Manager
Hosting
Hostinger

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on luby.co, including 11 speed issues and 1 conversion gap. 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