Tools & Wizards About Us

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

swayaustin.com

sway | modern thai restaurant in austin, texas

Page Load Speed

697 ms in total

First Response

32 ms

Resources Loaded

608 ms

Page Rendered

57 ms

About Website

Click here to check amazing Sway Austin content for United States. Otherwise, check out these important facts you probably never knew about swayaustin.com

sway is an award-winning modern thai restaurant, offering dine-in and takeout in austin, texas near westlake hills.

Visit swayaustin.com

Key Findings

We analyzed Swayaustin.com page load time and found that the first response time was 32 ms and then it took 665 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

swayaustin.com performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

swayaustin.com

32 ms

swaythai.com

37 ms

swaythai.com

118 ms

base

53 ms

page

90 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Swayaustin.com, 37% (11 requests) were made to Swaythai.com and 33% (10 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (207 ms) relates to the external source Swaythai.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 14.6 kB (48%)

Content Size

30.7 kB

After Optimization

16.0 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Swayaustin.com main page is 30.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 16.5 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 9.9 kB

  • Original 14.1 kB
  • After minification 13.2 kB
  • After compression 4.2 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 9.9 kB or 70% of the original size.

Image Optimization

-29%

Potential reduce by 4.7 kB

  • Original 16.5 kB
  • After minification 11.8 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. Obviously, Sway Austin needs image optimization as it can save up to 4.7 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

Number of requests can be reduced by 13 (76%)

Requests Now

17

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

swayaustin.com accessibility score

96

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

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

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

swayaustin.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 Swayaustin.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 Swayaustin.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 PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: