Website review, no card needed
americinn.com website review
Visit site (opens in a new tab)Reviewed 29 October 202652 issues · 91 checks
This review found 52 issues worth fixing on americinn.com, 22 of them high impact, across 91 checks. The most urgent: use efficient cache lifetimes. 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
57FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.3 s |
| May 16, 2026 | 4.3 s |
| May 23, 2026 | 4.3 s |
| May 30, 2026 | 4.2 s |
| Jun 6, 2026 | 4.2 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.2 s |
| Jul 11, 2026 | 4.1 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 4.1 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 4.1 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.1 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 4.1 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.3 s |
| Oct 17, 2026 | 4.4 s |
| Oct 24, 2026 | 4.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 319 ms |
| May 16, 2026 | 335 ms |
| May 23, 2026 | 347 ms |
| May 30, 2026 | 362 ms |
| Jun 6, 2026 | 372 ms |
| Jun 13, 2026 | 379 ms |
| Jun 20, 2026 | 379 ms |
| Jun 27, 2026 | 379 ms |
| Jul 4, 2026 | 381 ms |
| Jul 11, 2026 | 379 ms |
| Jul 18, 2026 | 380 ms |
| Jul 25, 2026 | 388 ms |
| Aug 1, 2026 | 397 ms |
| Aug 8, 2026 | 409 ms |
| Aug 15, 2026 | 421 ms |
| Aug 22, 2026 | 426 ms |
| Aug 29, 2026 | 426 ms |
| Sep 5, 2026 | 425 ms |
| Sep 12, 2026 | 423 ms |
| Sep 19, 2026 | 421 ms |
| Sep 26, 2026 | 418 ms |
| Oct 3, 2026 | 416 ms |
| Oct 10, 2026 | 421 ms |
| Oct 17, 2026 | 424 ms |
| Oct 24, 2026 | 427 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
1.0 s
2.1 s
3.1 s
4.2 s
5.2 s
6.2 s
7.3 s
8.3 s
Speed
Use efficient cache lifetimes
8.5 s · 5.4 MB59 files are served with short cache lifetimes, so returning visitors download them again (5.4 MB).
Improve image delivery
6.0 s · 5.3 MB8 images could be 5.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.0 s faster on a phone.
Reduce unused JavaScript
3.3 s · 2.6 MBAbout 2.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Render-blocking requests
4.2 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Google Tag Manager adds 2.5 s
2.5 sGoogle Tag Manager costs a phone 2.5 s of main-thread work and 3.3 MB 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: 23
23/100Your mobile performance score is 23. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 10.0 s
A phone's processor spends 10.0 s on main-thread work while loading, 6.6 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, Adobe Tag Manager and ofgreencolumn.com and others), adding 4.7 MB and 3.7 s of main-thread time.
Reduce unused CSS
450 ms · 96 KiBAbout 96 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Legacy JavaScript
450 ms · 67 KiBPolyfills for old browsers add 67 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 498 ms. During a long task the page ignores taps.
Adobe Tag Manager adds 292 ms
292 msAdobe Tag Manager costs a phone 292 ms of main-thread work and 297 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,725 HTML elements
The page has 2,725 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Maps adds 132 ms
132 msGoogle Maps costs a phone 132 ms of main-thread work and 379 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
20 KiB20 KiB could be saved by minifying JavaScript.
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: 8 ms
8 msYour server sent the HTML in 8 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 CLS: 0.66
0.66For real visitors the layout shifts by 0.66 (75th percentile). Good is under 0.1.
First Contentful Paint: 9.8 s
9.8 sThe first text or image appears after 9.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 29.0 s
29.0 sYour largest element takes 29.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 18.6 s
18.6 sVisually, the page fills in at 18.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 62.5 s
62.5 sThe page becomes fully interactive after 62.5 s. Good is under 3.8 s.
Total Blocking Time: 2.5 s
2.5 sScripts block taps and scrolling for 2.5 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 463 ms
463 msReal visitors wait 463 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 319 ms to 427 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
32 images without width and height
32 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.115
0.115The layout shifts by 0.115 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.3 s to 4.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user TTFB: 489 ms
489 msReal visitors wait 489 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 16.3 MB in 422 requests
16.3 MBYour homepage downloads 16.3 MB in 422 requests on a phone: images 9.3 MB (91), scripts 6.4 MB (114) and other files 261 KiB (179). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.9 MB together. On a phone connection a single image that size takes seconds.
2 images in older formats
2 images (1.9 MB) 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 4.6 g of CO₂ per visit
4.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.63 g of CO₂e: 555.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
<html> element must have a valid value for the lang attribute (1 element)
<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Page language is “en_US”
The page declares lang=“en_US”, which is not a usable language code, so screen readers and translation tools guess.
Users should be able to zoom and scale the text up to 500% (1 element)
Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
16 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 19 WCAG 2.2 A/AA and best-practice rules on the phone render: 16 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (161 characters)
Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
120 internal links, 27 external
The homepage links to 120 pages on americinn.com and 27 external pages.
5 checks passed
Title: 59 characters
Your title is a healthy 59 characters: “AmericInn by Wyndham - Hotel Rooms, Discount Rates, & Deals”.
Canonical URL set
The canonical URL is https://www.wyndhamhotels.com/americinn.
Structured data in place
Structured data found: Brand and Organization.
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.wyndhamhotels.com/sitemap.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,026 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.wyndhamhotels.com/llms.txt (16 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.wyndhamhotels.com/americinn/find-reservation, which answers with an error. Visitors hit a dead end and search engines drop it.
1 linked page hidden from search
https://www.wyndhamhotels.com/wyndham-rewards/my-favorite is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://www.wyndhamhotels.com/wyndham-rewards/my-favorite and https://www.wyndhamhotels.com/wyndham-rewards/hotel-deals/earn-4x-points have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.wyndhamhotels.com/wyndham-rewards, https://www.wyndhamhotels.com/wyndham-rewards/my-favorite and https://www.wyndhamhotels.com/wyndham-rewards/hotel-deals/earn-4x-points 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 55 found) and read each the way a search engine does.
3 checks passed
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 5 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://play.google.com/intl/en_us/badges/images/generic/en_badge_web_generic.png.
41 small tap targets
41 of 84 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 4 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Access to CSS stylesheet at 'https://api.tnapplications.com/assets/d15498b6-70cd-4bae-a99e-a37402060541/flow-container.…”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 13-field form
Your longest form asks for 13 fields (1 required). Every extra field lowers completion.
About 1,979 words of copy
The homepage carries about 1,979 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More” and “LEARN MORE”.
21 calls to action
The homepage has 21 calls to action, for example “Toggle search book”, “BOOK NOW” and “LEARN MORE”.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 2 trust badges.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
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
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 4 mores (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.
65 cookies set on arrival
65Opening the homepage sets 65 cookies (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.
56 other companies contacted
Loading the homepage contacts 56 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 americinn.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Hosting
- Akamai
Company
- Founded
- 1984
- Headquarters
- Chanhassen
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on americinn.com, including 27 speed issues, 3 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.