Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

austinchronicle.com

Austin News, Events, Restaurants, Music - The Austin Chronicle

Page Load Speed

3.3 sec in total

First Response

133 ms

Resources Loaded

2.9 sec

Page Rendered

284 ms

austinchronicle.com screenshot

About Website

Welcome to austinchronicle.com homepage info - get ready to check Austin Chronicle best content for United States right away, or after learning these important things about austinchronicle.com

The Austin Chronicle is an independent, locally owned and operated alternative newsweekly that reflects the heart and soul of Austin, Texas.

Visit austinchronicle.com

Key Findings

We analyzed Austinchronicle.com page load time and found that the first response time was 133 ms and then it took 3.2 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

austinchronicle.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value1,530 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

austinchronicle.com

133 ms

www.austinchronicle.com

2357 ms

fonts.css

215 ms

font-awesome.min.css

124 ms

ac-style.css

129 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 48% of them (41 requests) were addressed to the original Austinchronicle.com, 28% (24 requests) were made to and 2% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Austinchronicle.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 771.7 kB (30%)

Content Size

2.5 MB

After Optimization

1.8 MB

In fact, the total size of Austinchronicle.com main page is 2.5 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 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 96.1 kB

  • Original 113.1 kB
  • After minification 99.6 kB
  • After compression 17.0 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 13.5 kB, which is 12% 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 96.1 kB or 85% of the original size.

Image Optimization

-7%

Potential reduce by 85.7 kB

  • Original 1.2 MB
  • After minification 1.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. Austin Chronicle images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 173.8 kB

  • Original 289.4 kB
  • After minification 288.6 kB
  • After compression 115.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 173.8 kB or 60% of the original size.

CSS Optimization

-46%

Potential reduce by 416.1 kB

  • Original 905.1 kB
  • After minification 886.3 kB
  • After compression 489.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. Austinchronicle.com needs all CSS files to be minified and compressed as it can save up to 416.1 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (57%)

Requests Now

58

After Optimization

25

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

Accessibility Review

austinchronicle.com accessibility score

70

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements 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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

austinchronicle.com best practices score

75

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

SEO Factors

austinchronicle.com SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Austinchronicle.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 Austinchronicle.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 description is not detected on the main page of Austin Chronicle. 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: