Access alofttempe.com. Tempe, Arizona Hotels near Scottsdale

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value22.1 s

0/100

25%

SI (Speed Index)

Value23.3 s

0/100

10%

TBT (Total Blocking Time)

Value24,330 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.075

95/100

15%

TTI (Time to Interactive)

Value55.3 s

0/100

10%

alofttempe.com

456 ms

www.alofttempe.com

31 ms

1669 ms

marriottCommon.js

72 ms

d4222273e0406f938b23f5e9f0ee55b0f0aafa2feb045

164 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Alofttempe.com, 62% (21 requests) were made to Marriott.com and 26% (9 requests) were made to Cache.marriott.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Marriott.com.

Content Size

2.3 MB

After Optimization

1.0 MB

In fact, the total size of Alofttempe.com main page is 2.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 208.1 kB

Original 250.2 kB
After minification 211.4 kB
After compression 42.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 38.9 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 208.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 215 B

Original 590.1 kB
After minification 589.9 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Aloft Tempe images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 1.1 MB

Original 1.5 MB
After minification 1.5 MB
After compression 393.7 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.1 MB or 73% of the original size.

Requests Now

After Optimization

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aloft Tempe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

High

ARIA IDs are not unique

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alofttempe.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Alofttempe.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph data is detected on the main page of Aloft Tempe. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: