intownsuites.com website review

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.2 s faster on a phone.

23 files are served with short cache lifetimes, so returning visitors download them again (673 KiB).

36 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.

Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Google Maps and others), adding 3.2 MB and 896 ms of main-thread time.

3 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 130 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 440 ms faster on a phone.

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

Google CDN costs a phone 251 ms of main-thread work and 818 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.

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

Vimeo costs a phone 86 ms of main-thread work and 1.2 MB 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.

Google Maps costs a phone 105 ms of main-thread work and 393 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.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

3 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 20.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ITS-FamilyCTP”.

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

Visually, the page fills in at 9.9 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 4.3 s on a phone. Good is under 1.8 s.

Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 203 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

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

11 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 141 ms to 152 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.5 MB in 170 requests on a phone: scripts 3.3 MB (72), images 2.3 MB (35) and other files 366 KiB (26). Under 2 MB keeps phones on slow connections fast.

miles-manwaring-iWpF3D_M-1g-unsplash-scaled.jpg weighs 657 KiB. On a phone connection a single image that size takes seconds.

5 images (1.8 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.

ITS-FamilyCTP.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

3 elements have a tabindex above 0, which scrambles the keyboard order.

1 tap target is too small or too close together to hit reliably with a finger.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h3, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

Your meta description is 172 characters; Google truncates after about 160, so the end of your pitch is cut.

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 62 pages on intownsuites.com and 5 external pages.

https://www.intownsuites.com/veterans is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.intownsuites.com/veterans has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.intownsuites.com/about-intown-suites/corporate-housing, whose canonical is https://www.intownsuites.com/group-travel. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.intownsuites.com/reservation and https://www.intownsuites.com/renew-online have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://www.intownsuites.com/.

4 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Bootstrap's JavaScript requires jQuery version 1.9.1 or higher, but lower than version 3”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage carries about 294 words of visible text.

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

Opening the homepage sets 15 cookies, 2 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.