Tools & Wizards About Us
sumosanantonio.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

sumosanantonio.com

Sumo Japanese Steakhouse | The Best Steakhouse in San Antonio

Page Load Speed

3 sec in total

First Response

136 ms

Resources Loaded

2 sec

Page Rendered

829 ms

sumosanantonio.com screenshot

About Website

Click here to check amazing Sumo San Antonio content. Otherwise, check out these important facts you probably never knew about sumosanantonio.com

Sumo Japanese Steakhouse is a traditional Japanese Hibachi Steakhouse and the best Steakhouse in San Antonio with Japanese style cooking known as Teppanyaki.

Visit sumosanantonio.com

Key Findings

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

sumosanantonio.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value37.1 s

0/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value4,710 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value30.2 s

0/100

10%

Network Requests Diagram

sumosanantonio.com

136 ms

sumosanantonio.com

231 ms

css

37 ms

style2.css

75 ms

modernizr.min.js

155 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 44% of them (29 requests) were addressed to the original Sumosanantonio.com, 11% (7 requests) were made to 88restaurants.com and 11% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Sumosanantonio.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 185.4 kB (3%)

Content Size

6.7 MB

After Optimization

6.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sumosanantonio.com main page is 6.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.6 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 47.6 kB

  • Original 61.6 kB
  • After minification 49.2 kB
  • After compression 14.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 12.4 kB, which is 20% 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 47.6 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 129.0 kB

  • Original 5.6 MB
  • After minification 5.5 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. Sumo San Antonio images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 5.2 kB

  • Original 851.8 kB
  • After minification 851.8 kB
  • After compression 846.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 3.6 kB

  • Original 127.0 kB
  • After minification 127.0 kB
  • After compression 123.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. Sumosanantonio.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (44%)

Requests Now

55

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sumo San Antonio. 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 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

sumosanantonio.com

sumosanantonio.com

136 ms

sumosanantonio.com

sumosanantonio.com

231 ms

css

css

37 ms

style2.css

style2.css

75 ms

modernizr.min.js

modernizr.min.js

155 ms

jquery.min.js

jquery.min.js

29 ms

script.min.js

script.min.js

216 ms

all.js

all.js

18 ms

ga.js

ga.js

24 ms

all.js

all.js

26 ms

__utm.gif

__utm.gif

31 ms

S4A3JYmCMHM

S4A3JYmCMHM

179 ms

15

15

665 ms

contact_forms

contact_forms

661 ms

embed

embed

664 ms

logo_dark_mobile.png

logo_dark_mobile.png

159 ms

home-1.jpg

home-1.jpg

639 ms

sumo14.jpg

sumo14.jpg

655 ms

gg2.jpg

gg2.jpg

719 ms

twitter.png

twitter.png

639 ms

facebook.png

facebook.png

292 ms

instagram.png

instagram.png

639 ms

navy.png

navy.png

699 ms

kobeashi_50w.png

kobeashi_50w.png

649 ms

menu-background.jpg

menu-background.jpg

650 ms

tt10.jpg

tt10.jpg

697 ms

grey-sandbag.jpg

grey-sandbag.jpg

651 ms

tt1.jpg

tt1.jpg

994 ms

tt2.jpg

tt2.jpg

656 ms

tt9.jpg

tt9.jpg

700 ms

tt11.jpg

tt11.jpg

699 ms

tt12.jpg

tt12.jpg

996 ms

tt13.jpg

tt13.jpg

997 ms

tt14.jpg

tt14.jpg

1001 ms

logo-drk.png

logo-drk.png

990 ms

svg-holder.html

svg-holder.html

889 ms

ajax-loader.gif

ajax-loader.gif

1050 ms

about-para.jpg

about-para.jpg

1053 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

109 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

117 ms

vm8vdRfvXFLG3OLnsO15WYS5DG74wNc.ttf

vm8vdRfvXFLG3OLnsO15WYS5DG74wNc.ttf

160 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

156 ms

EJRSQgYoZZY2vCFuvAnt66qSVy4.ttf

EJRSQgYoZZY2vCFuvAnt66qSVy4.ttf

161 ms

slick.woff

slick.woff

1047 ms

www-player.css

www-player.css

13 ms

www-embed-player.js

www-embed-player.js

61 ms

base.js

base.js

147 ms

ad_status.js

ad_status.js

453 ms

hkwQPN6l4_SNpHVtjw8vAhWItmV3wkCVMuKaKCsfQ0c.js

hkwQPN6l4_SNpHVtjw8vAhWItmV3wkCVMuKaKCsfQ0c.js

138 ms

embed.js

embed.js

87 ms

application-8c87bb2c6997763e37e250d6ce8df67bb7be6d00a2067c6ae0ac9fc81ca76e56.css

application-8c87bb2c6997763e37e250d6ce8df67bb7be6d00a2067c6ae0ac9fc81ca76e56.css

77 ms

application-1594ca6d.css

application-1594ca6d.css

317 ms

application-d67d94944e9142f1fd49.js

application-d67d94944e9142f1fd49.js

553 ms

restaurants-cdb49b5618bc5a753fe2.js

restaurants-cdb49b5618bc5a753fe2.js

543 ms

css2

css2

74 ms

js

js

395 ms

api.js

api.js

374 ms

flatpickr_widget-e227448f49b9fd69b13bedcf33ad74e8e4239dcd234024f25a6d6786b82c963c.css

flatpickr_widget-e227448f49b9fd69b13bedcf33ad74e8e4239dcd234024f25a6d6786b82c963c.css

381 ms

js

js

539 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

229 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

228 ms

id

id

239 ms

Create

Create

30 ms

search.js

search.js

51 ms

geometry.js

geometry.js

63 ms

main.js

main.js

64 ms

Accessibility Review

sumosanantonio.com accessibility score

84

Accessibility Issues

ARIA

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.

Impact

Issue

High

ARIA input fields do not have accessible names

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.

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

sumosanantonio.com SEO score

92

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sumosanantonio.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Sumosanantonio.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

sumosanantonio.com

Open Graph description is not detected on the main page of Sumo San Antonio. 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: