Tools & Wizards About Us
21astor.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

21astor.com

21 Astor: Luxury Apartments In Portland | Live Near Downtown

Page Load Speed

3.7 sec in total

First Response

718 ms

Resources Loaded

2.2 sec

Page Rendered

833 ms

21astor.com screenshot

About Website

Visit 21astor.com now to see the best up-to-date 21 Astor content and also check out these interesting facts you probably never knew about 21astor.com

21 Astor's Luxury Apartments In Portland. Located In The Alphabet District. Merry Modern Elegance With Classic Craftsmanship. Contact Us For More Information.

Visit 21astor.com

Key Findings

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

Performance Metrics

21astor.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value16.1 s

0/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

21astor.com

718 ms

css

40 ms

font-awesome.min.css

46 ms

owl.carousel.min.css

57 ms

autoptimize_9fe5d7651b13a2b05c92f0cde6e3c93a.css

135 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 65% of them (31 requests) were addressed to the original 21astor.com, 8% (4 requests) were made to Cdnjs.cloudflare.com and 6% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (857 ms) belongs to the original domain 21astor.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 111.6 kB (4%)

Content Size

3.0 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 21astor.com main page is 3.0 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. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 27.0 kB

  • Original 34.5 kB
  • After minification 26.7 kB
  • After compression 7.6 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 7.8 kB, which is 23% 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 27.0 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 18.9 kB

  • Original 2.8 MB
  • After minification 2.8 MB

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. 21 Astor images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 61.1 kB

  • Original 170.1 kB
  • After minification 170.1 kB
  • After compression 109.0 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 61.1 kB or 36% of the original size.

CSS Optimization

-14%

Potential reduce by 4.6 kB

  • Original 32.0 kB
  • After minification 32.0 kB
  • After compression 27.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. 21astor.com needs all CSS files to be minified and compressed as it can save up to 4.6 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (40%)

Requests Now

42

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

21astor.com

21astor.com

718 ms

css

css

40 ms

font-awesome.min.css

font-awesome.min.css

46 ms

owl.carousel.min.css

owl.carousel.min.css

57 ms

autoptimize_9fe5d7651b13a2b05c92f0cde6e3c93a.css

autoptimize_9fe5d7651b13a2b05c92f0cde6e3c93a.css

135 ms

autoptimize_b6fd9ec333120ec9786fbfb172de1531.css

autoptimize_b6fd9ec333120ec9786fbfb172de1531.css

192 ms

jquery.min.js

jquery.min.js

34 ms

jquery-migrate-3.0.1.min.js

jquery-migrate-3.0.1.min.js

27 ms

gtm4wp-contact-form-7-tracker.js

gtm4wp-contact-form-7-tracker.js

207 ms

owl.carousel.min.js

owl.carousel.min.js

62 ms

what-input.js

what-input.js

231 ms

foundation.js

foundation.js

286 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

304 ms

app.js

app.js

239 ms

scripts.js

scripts.js

282 ms

wp-embed.min.js

wp-embed.min.js

303 ms

gtm.js

gtm.js

162 ms

robert-ball.png

robert-ball.png

118 ms

logo-header-hover.png

logo-header-hover.png

116 ms

logo.png

logo.png

117 ms

1_Detail-Shots-21-Astor-Condo.jpg

1_Detail-Shots-21-Astor-Condo.jpg

664 ms

timthumb.php

timthumb.php

340 ms

timthumb.php

timthumb.php

651 ms

timthumb.php

timthumb.php

857 ms

timthumb.php

timthumb.php

628 ms

timthumb.php

timthumb.php

555 ms

timthumb.php

timthumb.php

549 ms

icon-walk.png

icon-walk.png

612 ms

icon-transit.png

icon-transit.png

621 ms

icon-bike.png

icon-bike.png

676 ms

EcoHome_Logo.png

EcoHome_Logo.png

170 ms

Leed_Logo.png

Leed_Logo.png

171 ms

info-logo2-1.png

info-logo2-1.png

170 ms

info-logo3.png

info-logo3.png

685 ms

logo-footer-hover.png

logo-footer-hover.png

692 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

102 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

103 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

102 ms

peignot-webfont.woff

peignot-webfont.woff

660 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

59 ms

refill

refill

714 ms

ajax-loader.gif

ajax-loader.gif

628 ms

js

js

80 ms

fbevents.js

fbevents.js

33 ms

analytics.js

analytics.js

86 ms

collect

collect

20 ms

collect

collect

36 ms

collect

collect

4 ms

Accessibility Review

21astor.com accessibility score

88

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

21astor.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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

21astor.com SEO score

86

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

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

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 21astor.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 21astor.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

21astor.com

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