Website review, no card needed
citrusbug.com website review
Visit site (opens in a new tab)Reviewed 10 November 202620 issues · 82 checks
This review found 20 issues worth fixing on citrusbug.com, 3 of them high impact, across 82 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
90AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 4.0 s |
| May 30, 2026 | 4.0 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 2.9 s |
| Oct 31, 2026 | 2.7 s |
| Nov 7, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 247 ms |
| May 30, 2026 | 284 ms |
| Jun 6, 2026 | 284 ms |
| Jun 13, 2026 | 260 ms |
| Jun 20, 2026 | 227 ms |
| Jun 27, 2026 | 223 ms |
| Jul 4, 2026 | 228 ms |
| Jul 11, 2026 | 228 ms |
| Jul 18, 2026 | 195 ms |
| Jul 25, 2026 | 176 ms |
| Aug 1, 2026 | 136 ms |
| Aug 8, 2026 | 139 ms |
| Aug 15, 2026 | 139 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 139 ms |
| Sep 5, 2026 | 144 ms |
| Sep 12, 2026 | 175 ms |
| Sep 19, 2026 | 163 ms |
| Sep 26, 2026 | 172 ms |
| Oct 3, 2026 | 161 ms |
| Oct 10, 2026 | 139 ms |
| Oct 17, 2026 | 128 ms |
| Oct 24, 2026 | 127 ms |
| Oct 31, 2026 | 144 ms |
| Nov 7, 2026 | 126 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
Speed
Use efficient cache lifetimes
583 KiB28 files are served with short cache lifetimes, so returning visitors download them again (583 KiB).
Render-blocking requests
400 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
2,239 HTML elements
The page has 2,239 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
175 KiB6 images could be 175 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
92 KiBAbout 92 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
2 third-party services on the page
2 third-party services load with your homepage (Cloudflare and cloudfront.net), adding 11 KiB and 9 ms of main-thread time.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
3 checks passed
Mobile performance score: 100
100/100Your mobile performance score is 100. That is in Google's “good” band (90 and up).
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 82 ms of it running JavaScript. That is comfortably low.
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
57 images without width and height
57 images have no width and height attributes, so the layout jumps as each one loads.
10 checks passed
Real-user INP: 125 ms
125 msReal visitors wait 125 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 49% faster for real visitors
-49%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 247 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 34% faster for real visitors
-34%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 4.0 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 2.8 s
2.8 sVisually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Largest Contentful Paint: 1.2 s
1.2 sYour largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Turn Business Challenges Into Practical AI and Digital Solu…”.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 1.2 s
1.2 sThe page is fully interactive after 1.2 s.
Images and page weight
1 image far larger than shown
79 KiB1 image is downloaded at several times the size a phone draws it, for example Airbnb_Logo.png at 2,560 px wide, shown at 83 px. Resized copies would save about 79 KiB.
3 images in older formats
3 images (149 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.
About 0.3 g of CO₂ per visit
0.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.26 g of CO₂e: 31.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 935 KiB in 31 requests
935 KiBYour homepage downloads 935 KiB in 31 requests on a phone: fonts 496 KiB (5), images 259 KiB (17) and stylesheets 87 KiB (3). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
46 text elements with low contrast
46 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 92 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (166 characters)
Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (BreadcrumbList, Organization, ProfessionalService and WebPage) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("{search_term_string}")”.
167 internal links, 13 external
The homepage links to 167 pages on citrusbug.com and 13 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Turn Business Challenges Into Practical AI and Digital Solutions”.
Title: 46 characters
Your title is a healthy 46 characters: “Citrusbug: Award-Winning AI Development Agency”.
Canonical URL set
The canonical URL is https://citrusbug.com/.
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://citrusbug.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://citrusbug.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.
3 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (3,888 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 126 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
5 small tap targets
5 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 distorted images
6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
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
A 9-field form
Your longest form asks for 9 fields (6 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 1,352 words of copy
The homepage carries about 1,352 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start a Conversation →”.
4 calls to action
The homepage has 4 calls to action, for example “Contact Us”, “Start a Conversation →” and “Book an AI Readiness Discovery Call →”.
Social proof on the page
Social proof on the homepage: 144 testimonial or review blocks, 19 customer or partner logos, a star rating, 2 trust badges and “31M+ patients”.
Analytics in place
Analytics detected: Google Analytics, Microsoft Clarity, LinkedIn Insight and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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.
2 other companies contacted
Loading the homepage contacts 2 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 citrusbug.com, 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
- jQuery
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on citrusbug.com, including 8 speed issues, 2 SEO 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.