intervalworld.com website review

11 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.1 s faster on a phone.

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

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

About 283 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

56 KiB could be saved by minifying JavaScript.

Facebook costs a phone 269 ms of main-thread work and 223 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.

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

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

3 third-party services load with your homepage (Facebook, Optanon and Google Fonts), adding 480 KiB and 434 ms of main-thread time.

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

17 KiB could be saved by minifying CSS.

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

Desktop scores 78 but mobile only 31. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

For real visitors the layout shifts by 0.79 (75th percentile). Good is under 0.1.

The layout shifts by 1.372 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your largest element takes 14.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cruise Month”.

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

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

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

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

Real visitors wait 850 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

8 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-03, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

interval_travel_mobileslider.jpg weighs 817 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.7 MB in 67 requests on a phone: images 1.8 MB (28), scripts 716 KiB (21) and stylesheets 69 KiB (6). Under 2 MB keeps phones on slow connections fast.

6 images (1.6 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.

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

8 tap targets are too small or too close together to hit reliably with a finger.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

12 images have no alt text, which hurts accessibility and image search.

2 visible links have no text or label, so screen readers cannot say where they go.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Elements with visible text labels do not have matching accessible names. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 29 characters: “Interval International | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.intervalworld.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at intervalworld.com/robots.txt, the first file search crawlers ask for.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 59 pages on intervalworld.com and 10 external pages.

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.

There is no https://www.intervalworld.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.

https://www.intervalworld.com/web/my/info/ownership, https://www.intervalworld.com/web/my/info/ownership/overview, https://www.intervalworld.com/web/my/info/ownership/about, https://www.intervalworld.com/web/my/info/planning, https://www.intervalworld.com/web/my/info/planning/magazine and https://www.intervalworld.com/web/my/info/planning/community and 7 others have no <title>, so Google invents the link text in results.

https://www.intervalworld.com/web/my/home and https://www.intervalworld.com/web/cs all use the title “Interval International | Home”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.intervalworld.com/web/cs, https://www.intervalworld.com/web/my/info/ownership, https://www.intervalworld.com/web/my/info/ownership/overview, https://www.intervalworld.com/web/my/info/ownership/about, https://www.intervalworld.com/web/my/info/planning and https://www.intervalworld.com/web/my/info/planning/magazine and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.intervalworld.com/web/my/info/ownership, https://www.intervalworld.com/web/my/info/ownership/overview, https://www.intervalworld.com/web/my/info/ownership/about, https://www.intervalworld.com/web/my/info/planning, https://www.intervalworld.com/web/my/info/planning/magazine and https://www.intervalworld.com/web/my/info/planning/community and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.intervalworld.com/web/cs, https://www.intervalworld.com/web/my/info/planning/community, https://www.intervalworld.com/web/my/info/planning/tracker, https://www.intervalworld.com/web/my/info/benefits, https://www.intervalworld.com/web/my/info/benefits/exchange and https://www.intervalworld.com/web/my/info/benefits/getaways took over 3 s to send their HTML from our server.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

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

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

1 error was logged to the browser console while the page loaded, for example “Loading the script 'https://s.go-mpulse.net/boomerang/D4S6W-DSJHP-LGD8Z-HZ8VR-7735B' violates the following Content Sec…”.

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 126 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads 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.

Opening the homepage sets 11 cookies (measured from a US location before any click).

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