Website review, no card needed
eaglewoodresort.com website review
Visit site (opens in a new tab)Reviewed 20 October 202628 issues · 84 checks
This review found 28 issues worth fixing on eaglewoodresort.com, 12 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.1 s |
| May 9, 2026 | 1.1 s |
| May 16, 2026 | 1.0 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 137 ms |
| May 9, 2026 | 140 ms |
| May 16, 2026 | 136 ms |
| May 23, 2026 | 141 ms |
| May 30, 2026 | 142 ms |
| Jun 6, 2026 | 144 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 144 ms |
| Jul 4, 2026 | 141 ms |
| Jul 11, 2026 | 140 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 139 ms |
| Aug 8, 2026 | 140 ms |
| Aug 15, 2026 | 139 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 140 ms |
| Sep 5, 2026 | 143 ms |
| Sep 12, 2026 | 149 ms |
| Sep 19, 2026 | 145 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 149 ms |
| Oct 10, 2026 | 150 ms |
| Oct 17, 2026 | 150 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
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.1 s
2.7 s
3.2 s
3.8 s
4.3 s
Speed
Render-blocking requests
1.6 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Google Tag Manager adds 1.0 s
1.0 sGoogle Tag Manager costs a phone 1.0 s of main-thread work and 799 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.
Mobile performance score: 44
44/100Your mobile performance score is 44 (desktop: 46). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, elfsight.com and flip.to and others), adding 1.7 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
150 ms · 634 KiBAbout 634 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
576 KiB10 files are served with short cache lifetimes, so returning visitors download them again (576 KiB).
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 469 ms. During a long task the page ignores taps.
elfsight.com adds 190 ms
190 mselfsight.com costs a phone 190 ms of main-thread work and 472 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.
Improve image delivery
250 ms · 219 KiB4 images could be 219 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Reduce unused CSS
209 KiBAbout 209 KiB of CSS is downloaded but never applied on this page.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need.
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: 193 ms
193 msYour server sent the HTML in 193 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 19.7 s
19.7 sThe page becomes fully interactive after 19.7 s. Good is under 3.8 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 5.1 s
5.1 sYour largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “EXPLORE EXCITING OPTIONS THROUGHOUT THE SEASONS With comfor…”.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 137 ms to 150 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 132 ms
132 msReal visitors wait 132 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.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 449 ms
449 msReal visitors wait 449 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 4.0 MB in 77 requests
4.0 MBYour homepage downloads 4.0 MB in 77 requests on a phone: scripts 1.8 MB (30), fonts 1.3 MB (7) and images 792 KiB (16). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
85 KiB2 images are downloaded at several times the size a phone draws them, for example 1.jpg at 1,080 px wide, shown at 351 px. Resized copies would save about 85 KiB.
3 images below the first screen load straight away
3 images further down the page (357 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (286 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 1.1 g of CO₂ per visit
1.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.14 g of CO₂e: 137.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
35 internal links, 10 external
The homepage links to 35 pages on eaglewoodresort.com and 10 external pages.
8 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Book yourself a getaway in Chicago, IL at Eaglewood Resort & Spa. Explore a variety of dining outlets, meeting spaces, …”.
One H1 headline
Your main headline reads: “Welcome to Eaglewood Resort”.
Title: 54 characters
Your title is a healthy 54 characters: “Resorts in Chicago IL - Eaglewood Resort & Spa Chicago”.
Canonical URL set
The canonical URL is https://www.eaglewoodresort.com/.
Structured data in place
Structured data found: Hotel.
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://www.eaglewoodresort.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.eaglewoodresort.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, description and contact details; logo and sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (516 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without an H1
https://www.eaglewoodresort.com/rooms.htm, https://www.eaglewoodresort.com/offers.htm, https://www.eaglewoodresort.com/dining.htm, https://www.eaglewoodresort.com/entertainment.htm, https://www.eaglewoodresort.com/amenities.htm and https://www.eaglewoodresort.com/spa.htm and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages with very little text
https://www.eaglewoodresort.com/rooms.htm, https://www.eaglewoodresort.com/offers.htm, https://www.eaglewoodresort.com/dining.htm, https://www.eaglewoodresort.com/entertainment.htm, https://www.eaglewoodresort.com/amenities.htm and https://www.eaglewoodresort.com/spa.htm and 9 others 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.
6 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.
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
4 small tap targets
4 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 545 words of copy
The homepage carries about 545 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: “LEARN MORE” and “CALL US”.
13 calls to action
The homepage has 13 calls to action, for example “Request Information”, “Book Now” and “Learn More”.
2 short forms
2 short forms (5 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
17 cookies set on arrival
17Opening the homepage sets 17 cookies (measured from a US location before any click).
27 other companies contacted
Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 eaglewoodresort.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
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 eaglewoodresort.com, including 15 speed issues, 1 SEO issue 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.