Tools & Wizards About Us
savageburrito.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

savageburrito.com

Homepage - Savage Burrito

Page Load Speed

2 sec in total

First Response

112 ms

Resources Loaded

1.2 sec

Page Rendered

593 ms

savageburrito.com screenshot

About Website

Visit savageburrito.com now to see the best up-to-date Savage Burrito content and also check out these interesting facts you probably never knew about savageburrito.com

Visit savageburrito.com

Key Findings

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

savageburrito.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value1,630 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

savageburrito.com

112 ms

savageburrito.com

199 ms

gtm.js

63 ms

aes5ina.css

161 ms

style.min.css

144 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 34% of them (12 requests) were addressed to the original Savageburrito.com, 14% (5 requests) were made to Res.cloudinary.com and 9% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (601 ms) relates to the external source Res.cloudinary.com.

Page Optimization Overview & Recommendations

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

Content Size

4.2 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-70%

Potential reduce by 369.0 kB

  • Original 528.0 kB
  • After minification 517.5 kB
  • After compression 159.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. 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 369.0 kB or 70% of the original size.

Image Optimization

-3%

Potential reduce by 100.0 kB

  • Original 3.3 MB
  • After minification 3.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. Savage Burrito images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 32.2 kB

  • Original 104.0 kB
  • After minification 104.0 kB
  • After compression 71.8 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 32.2 kB or 31% of the original size.

CSS Optimization

-2%

Potential reduce by 4.0 kB

  • Original 233.7 kB
  • After minification 233.7 kB
  • After compression 229.7 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. Savageburrito.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (64%)

Requests Now

28

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

savageburrito.com

savageburrito.com

112 ms

savageburrito.com

savageburrito.com

199 ms

gtm.js

gtm.js

63 ms

aes5ina.css

aes5ina.css

161 ms

style.min.css

style.min.css

144 ms

app.css

app.css

138 ms

utilities.css

utilities.css

248 ms

jquery.min.js

jquery.min.js

148 ms

jquery-migrate.min.js

jquery-migrate.min.js

97 ms

vendor.js

vendor.js

87 ms

app.js

app.js

104 ms

gsap.min.js

gsap.min.js

102 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

112 ms

3.0.0

3.0.0

110 ms

analytics.js

analytics.js

62 ms

destination

destination

93 ms

scevent.min.js

scevent.min.js

76 ms

css2

css2

70 ms

p.css

p.css

85 ms

collect

collect

40 ms

js

js

177 ms

sq-quesadillas.png

sq-quesadillas.png

298 ms

Hero-1-scaled.jpg

Hero-1-scaled.jpg

111 ms

why-savage-1.png

why-savage-1.png

161 ms

burritos_480.jpg

burritos_480.jpg

423 ms

sq-sides.png

sq-sides.png

586 ms

sq-bowls.png

sq-bowls.png

601 ms

dessert.jpg

dessert.jpg

444 ms

fbevents.js

fbevents.js

63 ms

dtag.js

dtag.js

420 ms

Hamurz_Rough.woff

Hamurz_Rough.woff

49 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFO_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFO_F.ttf

52 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFO_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFO_F.ttf

52 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE-_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE-_F.ttf

52 ms

d

d

24 ms

Accessibility Review

savageburrito.com accessibility score

95

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

savageburrito.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

savageburrito.com SEO score

93

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

savageburrito.com

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