Website review, no card needed
bobw.co website review
Visit site (opens in a new tab)Reviewed 2 November 202638 issues · 87 checks
This review found 38 issues worth fixing on bobw.co, 18 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 194 ms |
| May 23, 2026 | 191 ms |
| May 30, 2026 | 196 ms |
| Jun 6, 2026 | 196 ms |
| Jun 13, 2026 | 197 ms |
| Jun 20, 2026 | 197 ms |
| Jun 27, 2026 | 196 ms |
| Jul 4, 2026 | 196 ms |
| Jul 11, 2026 | 196 ms |
| Jul 18, 2026 | 200 ms |
| Jul 25, 2026 | 198 ms |
| Aug 1, 2026 | 197 ms |
| Aug 8, 2026 | 201 ms |
| Aug 15, 2026 | 209 ms |
| Aug 22, 2026 | 218 ms |
| Aug 29, 2026 | 228 ms |
| Sep 5, 2026 | 231 ms |
| Sep 12, 2026 | 226 ms |
| Sep 19, 2026 | 224 ms |
| Sep 26, 2026 | 219 ms |
| Oct 3, 2026 | 215 ms |
| Oct 10, 2026 | 212 ms |
| Oct 17, 2026 | 210 ms |
| Oct 24, 2026 | 211 ms |
| Oct 31, 2026 | 205 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
Reduce unused JavaScript
6.4 s · 935 KiBAbout 935 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.4 s faster on a phone.
Use efficient cache lifetimes
4.5 s · 1.0 MB53 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Google Tag Manager adds 1.4 s
1.4 sGoogle Tag Manager costs a phone 1.4 s of main-thread work and 708 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 13.6 s
A phone's processor spends 13.6 s on main-thread work while loading, 4.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Intercom and others), adding 1.4 MB and 2.4 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 547 ms. During a long task the page ignores taps.
Facebook adds 383 ms
383 msFacebook costs a phone 383 ms of main-thread work and 226 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.
Intercom adds 300 ms
300 msIntercom costs a phone 300 ms of main-thread work and 231 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.
2,479 HTML elements
The page has 2,479 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Duplicated JavaScript
150 ms · 13 KiB13 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
44 KiBAbout 44 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need.
Improve image delivery
17 KiB2 images could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 136 ms
136 msYour server sent the HTML in 136 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.
Largest Contentful Paint: 23.5 s
23.5 sYour largest element takes 23.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Let’s get one thing straight: you can’t eat them. Cookies a…”. Most of its time is element render delay (10.2 s).
Total Blocking Time: 4.8 s
4.8 sScripts block taps and scrolling for 4.8 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 23.5 s
23.5 sThe page becomes fully interactive after 23.5 s. Good is under 3.8 s.
Speed Index: 12.2 s
12.2 sVisually, the page fills in at 12.2 s (Speed Index). Good is under 3.4 s.
Real-user INP: 242 ms
242 msReal visitors wait 242 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 194 ms to 205 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 666 ms
666 msReal visitors wait 666 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.088
0.088The layout barely moves while loading (CLS 0.088, good is under 0.1).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 3.2 MB in 112 requests
3.2 MBYour homepage downloads 3.2 MB in 112 requests on a phone: scripts 2.1 MB (51), fonts 813 KiB (14) and images 185 KiB (17). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.5 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
58 text elements with low contrast
58 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA commands must have an accessible name (2 elements)
ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 55 images in the HTML carry an alt attribute.
51 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: 51 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
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 social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
11 links with vague text
11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
80 internal links, 15 external
The homepage links to 80 pages on bobw.co and 15 external pages.
4 checks passed
Title: 53 characters
Your title is a healthy 53 characters: “Bob W Aparthotels | The Best of Hotels and Apartments”.
Canonical URL set
The canonical URL is https://bobw.co/.
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://bobw.co/sitemap.xml.
AI search readiness
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.
Some text only appears after JavaScript runs
58%The HTML your server sends has 1,517 of the 2,596 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://bobw.co/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
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.
Other pages
5 pages without a meta description
https://bobw.co/locations, https://bobw.co/ways-to-stay, https://bobw.co/about-bob-w, https://bobw.co/notebook and https://bobw.co/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://bobw.co/locations/helsinki/helsinki-kamppi/spacious-studio, https://bobw.co/locations/copenhagen/copenhagen-osterbro/original-studio-2-people and https://bobw.co/locations/stockholm/bob-w-stockholm-norrmalm/spacious-studio use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://bobw.co/bobs-rewards, https://bobw.co/locations, https://bobw.co/ways-to-stay, https://bobw.co/about-bob-w, https://bobw.co/bob-s-offers and https://bobw.co/notebook and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
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 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56338289&tm=gtm002&Ver=2&mid=f669435a-f95e-466a-a450-46a12eecb104&bo=1&sid=84cd0cd0d68c11f1b868bdcf4bdefa3f&vid=84cd4e40d68c11f1b03931975c6f8594&vids=1&msclkid=N&pi=91.
7 small tap targets
7 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 2,596 words of copy
The homepage carries about 2,596 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us” and “Join Bob's Inner Circle”.
9 calls to action
The homepage has 9 calls to action, for example “Contact Us”, “join now” and “Book now”.
1 short form
A short form (5 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks, 10 customer or partner logos, a star rating and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
14 cookies set on arrival
14Opening the homepage sets 14 cookies (measured from a US location before any click).
20 other companies contacted
Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) loads with the page.
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 bobw.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on bobw.co, including 17 speed issues, 5 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.