Access brixat26.com. Brix at 26 Pittsburgh, PA

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value2,480 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.064

97/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

brixat26.com

40 ms

GetResource.ashx

13 ms

jquery.min.js

57 ms

jquery-ui.min.js

67 ms

global.min.js

451 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 17% of them (13 requests) were addressed to the original Brixat26.com, 32% (25 requests) were made to Cs-cdn.realpage.com and 22% (17 requests) were made to Capi.myleasestar.com. The less responsive or slowest element that took the longest time to load (7 sec) relates to the external source Cs-cdn.realpage.com.

Content Size

3.1 MB

After Optimization

2.7 MB

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

HTML Optimization

-81%

Potential reduce by 308.2 kB

Original 378.3 kB
After minification 357.9 kB
After compression 70.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 308.2 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 16.2 kB

Original 2.2 MB
After minification 2.1 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. Brix At 26 images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 69.2 kB

Original 526.3 kB
After minification 526.1 kB
After compression 457.1 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 69.2 kB or 13% of the original size.

CSS Optimization

-8%

Potential reduce by 3.2 kB

Original 42.2 kB
After minification 42.2 kB
After compression 39.0 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. Brixat26.com has all CSS files already compressed.

Requests Now

After Optimization

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brix At 26. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 16 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

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

Links do not have a discernible name

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

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

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 Brixat26.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 Brixat26.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

brixat26.com

Open Graph description is not detected on the main page of Brix At 26. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks:

Report Summary

Performance

Accessibility

Best Practices

SEO

Brix at 26 Pittsburgh, PA | Welcome Home

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

brixat26.com

GetResource.ashx

jquery.min.js

jquery-ui.min.js

global.min.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

brixat26.com

GetResource.ashx

jquery.min.js

jquery-ui.min.js

global.min.js

Accessibe.js

font-awesome.min.css

fontello.css

bootstrap.min.css

jquery.min.js

jquery-ui.js

jquery-migrate-1.4.1.js

bootstrap.min.js

TweenLite.min.js

ScrollMagic.min.js

animation.gsap.js

ScrollToPlugin.min.js

doorway.min.js

sps-v3.js

GetResource.ashx

css-vars-ponyfill@1

CommonData.js

jquery.fancybox.js

media-viewer.js

cookies-consent.js

jquery.flexslider-min.js

jquery.fancybox.css

jquery.mobile.toucheventsonly.min.js

masonry.pkgd.min.js

slick.css

slick.min.js

datepicker.js

GetResource.ashx

WebResource.axd

footer.js

ScriptResource.axd

ScriptResource.axd

loader.js

OtAutoBlock.js

otSDKStub.js

css

font

gtm.js