Tools & Wizards About Us
300alexander.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

300alexander.com

Apartments in Rochester, NY | 300 Alexander Apartments in Rochester, NY

Page Load Speed

2.1 sec in total

First Response

111 ms

Resources Loaded

1.5 sec

Page Rendered

501 ms

300alexander.com screenshot

About Website

Visit 300alexander.com now to see the best up-to-date 300 Alexander content for United States and also check out these interesting facts you probably never knew about 300alexander.com

Discover 300 Alexander Apartments, the best luxury apartments in Rochester, NY. Running along historic East Avenue from Alexander Street to Main Street, our nei

Visit 300alexander.com

Key Findings

We analyzed 300alexander.com page load time and found that the first response time was 111 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

300alexander.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value4.3 s

75/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

300alexander.com

111 ms

www.300alexander.com

294 ms

www.300alexander.com

279 ms

bootstrap.min.css

39 ms

css

85 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original 300alexander.com, 30% (11 requests) were made to Apollostore.blob.core.windows.net and 27% (10 requests) were made to Apollocdn.azureedge.net. The less responsive or slowest element that took the longest time to load (486 ms) relates to the external source Apollostore.blob.core.windows.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 372.6 kB (12%)

Content Size

3.0 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 300alexander.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. 70% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 27.1 kB

  • Original 35.2 kB
  • After minification 28.5 kB
  • After compression 8.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 6.7 kB, which is 19% 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.1 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 9.2 kB

  • Original 2.2 MB
  • After minification 2.2 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. 300 Alexander images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 331.7 kB

  • Original 712.7 kB
  • After minification 712.7 kB
  • After compression 381.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 331.7 kB or 47% of the original size.

CSS Optimization

-5%

Potential reduce by 4.6 kB

  • Original 85.1 kB
  • After minification 85.1 kB
  • After compression 80.5 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. 300alexander.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (36%)

Requests Now

28

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

300alexander.com

300alexander.com

111 ms

www.300alexander.com

www.300alexander.com

294 ms

www.300alexander.com

www.300alexander.com

279 ms

bootstrap.min.css

bootstrap.min.css

39 ms

css

css

85 ms

theme.css

theme.css

49 ms

site.css

site.css

212 ms

jquery.min.js

jquery.min.js

47 ms

js

js

90 ms

mapbox-gl.js

mapbox-gl.js

85 ms

api.js

api.js

83 ms

main.js

main.js

87 ms

bootstrap.min.js

bootstrap.min.js

85 ms

gtm.js

gtm.js

138 ms

logo-markiventerprises.png

logo-markiventerprises.png

128 ms

wheelchair.png

wheelchair.png

78 ms

paw.png

paw.png

78 ms

eho.png

eho.png

77 ms

wcag.png

wcag.png

79 ms

icon-poweredby.png

icon-poweredby.png

78 ms

layout.logo.e276079b-8752-47f4-9071-2fbe09acb08e.png

layout.logo.e276079b-8752-47f4-9071-2fbe09acb08e.png

96 ms

hero1.7eaf53ee-81ab-4a78-8da4-5853ea5de67f.jpg

hero1.7eaf53ee-81ab-4a78-8da4-5853ea5de67f.jpg

421 ms

review1.1.d1de5caf-b629-488a-bc6d-e25597f0a7f8-1.f85baa25-404a-47bd-9502-809142e5cd34.jpg

review1.1.d1de5caf-b629-488a-bc6d-e25597f0a7f8-1.f85baa25-404a-47bd-9502-809142e5cd34.jpg

233 ms

home-amen.4249b6e0-ab0a-4985-961b-95f0a8c04698.jpg

home-amen.4249b6e0-ab0a-4985-961b-95f0a8c04698.jpg

338 ms

marketing.homepage.floorplans.80c854c5-9edf-4a46-8d1c-e367478683c0.jpg

marketing.homepage.floorplans.80c854c5-9edf-4a46-8d1c-e367478683c0.jpg

333 ms

h-property.bec5abf4-b507-4532-b3ae-adb3aedcb867.jpg

h-property.bec5abf4-b507-4532-b3ae-adb3aedcb867.jpg

486 ms

extra.fe6c72d2-d8ce-4489-b4e0-8c829be60daa.jpg

extra.fe6c72d2-d8ce-4489-b4e0-8c829be60daa.jpg

448 ms

4.a7151b51-c988-4fe4-82c2-4691195203e5.jpg

4.a7151b51-c988-4fe4-82c2-4691195203e5.jpg

306 ms

5.a80fdf68-39b2-4ba0-a9d3-2729674b736f.jpg

5.a80fdf68-39b2-4ba0-a9d3-2729674b736f.jpg

380 ms

6.2da6eee9-a42b-4743-be6d-bb3e73124e7a.jpg

6.2da6eee9-a42b-4743-be6d-bb3e73124e7a.jpg

416 ms

recaptcha__en.js

recaptcha__en.js

81 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf

56 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFn8kEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFn8kEk30e0.ttf

66 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e0.ttf

76 ms

7Aujp_0qiz-afTfcIyoiGtm2P0wG05Fz4eqVxg.ttf

7Aujp_0qiz-afTfcIyoiGtm2P0wG05Fz4eqVxg.ttf

76 ms

7Aujp_0qiz-afTfcIyoiGtm2P0wG06Nz4eqVxg.ttf

7Aujp_0qiz-afTfcIyoiGtm2P0wG06Nz4eqVxg.ttf

76 ms

7Aujp_0qiz-afTfcIyoiGtm2P0wG089z4eqVxg.ttf

7Aujp_0qiz-afTfcIyoiGtm2P0wG089z4eqVxg.ttf

76 ms

Accessibility Review

300alexander.com accessibility score

98

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

Links do not have a discernible name

Best Practices

300alexander.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

300alexander.com SEO score

100

Search Engine Optimization Advices

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 300alexander.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 300alexander.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

300alexander.com

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