thirteenthfloor.com website review

102 files are served with short cache lifetimes, so returning visitors download them again (15.2 MB).

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

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

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

About 106 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 45 (desktop: 87). 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 Tag Manager, Facebook and TikTok and others), adding 895 KiB and 772 ms of main-thread time.

Google Tag Manager costs a phone 322 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

Desktop scores 87 but mobile only 45. 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.

2 KiB could be saved by minifying CSS.

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 25.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “World-Class Live Events and Immersive Experiences”.

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

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

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

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

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

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

Your homepage downloads 20.6 MB in 136 requests on a phone: media 15.2 MB (7), images 3.8 MB (37) and scripts 1.1 MB (35). Under 2 MB keeps phones on slow connections fast.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 82 characters, so Google will cut it off around 60: “Thirteenth Floor Entertainment Group | Home - Thirteenth Floor Entertainment Group”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 31 pages on thirteenthfloor.com and 0 external pages.

Your Organization JSON-LD is missing url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /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.

/beta declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/haunted-attractions, /interactive-immersive-experiences, /social-gaming, /creative-studio, /activations and /sponsorships and 1 other are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and /beta all use the title “Thirteenth Floor Entertainment Group | Home - Thirteenth Floor Entert…”. Search engines can't tell which page to show for a search, so each competes with the others.

/beta, /haunted-attractions, /interactive-immersive-experiences, /social-gaming, /creative-studio and /activations and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

The homepage carries about 321 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel, Snap Pixel and TikTok Pixel (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 9 cookies (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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.