Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

aloftpdx.com

Cascade Station Portland Hotel | Aloft Portland Airport at Cascade Station

Page Load Speed

4.1 sec in total

First Response

16 ms

Resources Loaded

3.1 sec

Page Rendered

1 sec

About Website

Welcome to aloftpdx.com homepage info - get ready to check Aloft Pdx best content right away, or after learning these important things about aloftpdx.com

Reserve your stay at our hotel near Cascade Station in Portland, offering complimentary Wi-Fi, a full-service bar and free shuttle to and from the airport.

Visit aloftpdx.com

Key Findings

We analyzed Aloftpdx.com page load time and found that the first response time was 16 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

aloftpdx.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value17.5 s

0/100

25%

SI (Speed Index)

Value17.7 s

0/100

10%

TBT (Total Blocking Time)

Value18,530 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value50.2 s

0/100

10%

Network Requests Diagram

aloftpdx.com

16 ms

463 ms

marriottCommon.js

89 ms

6e15e9b645406f938b23f5e9f0ee55b0f0aafa2feb045

102 ms

ruxitagentjs_ICA7NQVfhqrux_10297240712040816.js

66 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Aloftpdx.com, 64% (21 requests) were made to Marriott.com and 24% (8 requests) were made to Cache.marriott.com. The less responsive or slowest element that took the longest time to load (998 ms) relates to the external source Cache.marriott.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 332.5 kB (28%)

Content Size

1.2 MB

After Optimization

871.8 kB

In fact, the total size of Aloftpdx.com main page is 1.2 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. 55% of websites need less resources to load. Javascripts take 509.4 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 213.6 kB

  • Original 258.5 kB
  • After minification 218.9 kB
  • After compression 44.9 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 39.5 kB, which is 15% 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 213.6 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 215 B

  • Original 436.6 kB
  • After minification 436.3 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 Pdx images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 118.7 kB

  • Original 509.4 kB
  • After minification 508.8 kB
  • After compression 390.6 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 118.7 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (77%)

Requests Now

26

After Optimization

6

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

Accessibility Review

aloftpdx.com accessibility score

71

Accessibility Issues

ARIA

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.

Impact

Issue

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

Names and labels

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.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

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

Impact

Issue

High

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

Best Practices

aloftpdx.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

aloftpdx.com SEO score

74

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Mobile Friendly

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/).

Impact

Issue

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 Aloftpdx.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 Aloftpdx.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 Pdx. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: