Tools & Wizards About Us
whataburger13.com screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

whataburger13.com

What-A-Burger #13 | Restaurant| North Carolina

Page Load Speed

936 ms in total

First Response

49 ms

Resources Loaded

468 ms

Page Rendered

419 ms

whataburger13.com screenshot

About Website

Welcome to whataburger13.com homepage info - get ready to check What A Burger 13 best content right away, or after learning these important things about whataburger13.com

Dine on delicious and mouthwatering fast food from What A Burger 13. Our restaurant is located in Mount Pleasant, NC.

Visit whataburger13.com

Key Findings

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

Performance Metrics

whataburger13.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value3.4 s

90/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

whataburger13.com

49 ms

whataburger13.com

46 ms

style.min.css

23 ms

2-layout.css

40 ms

all.min.css

38 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 81% of them (38 requests) were addressed to the original Whataburger13.com, 11% (5 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Img1.wsimg.com. The less responsive or slowest element that took the longest time to load (184 ms) belongs to the original domain Whataburger13.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 145.1 kB (10%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whataburger13.com main page is 1.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. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 53.8 kB

  • Original 67.0 kB
  • After minification 65.6 kB
  • After compression 13.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 53.8 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 1.8 kB

  • Original 1.1 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. What A Burger 13 images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 87.7 kB

  • Original 203.3 kB
  • After minification 202.9 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 87.7 kB or 43% of the original size.

CSS Optimization

-2%

Potential reduce by 1.8 kB

  • Original 94.5 kB
  • After minification 94.4 kB
  • After compression 92.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. Whataburger13.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (73%)

Requests Now

37

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whataburger13.com

whataburger13.com

49 ms

whataburger13.com

whataburger13.com

46 ms

style.min.css

style.min.css

23 ms

2-layout.css

2-layout.css

40 ms

all.min.css

all.min.css

38 ms

animate.css

animate.css

29 ms

6ec54fc251eba294a08cce69b0589357-layout-bundle.css

6ec54fc251eba294a08cce69b0589357-layout-bundle.css

32 ms

style.min.css

style.min.css

44 ms

latest.css

latest.css

48 ms

GD-cORe-public.css

GD-cORe-public.css

71 ms

jquery.magnificpopup.min.css

jquery.magnificpopup.min.css

58 ms

base.min.css

base.min.css

53 ms

skin-6400f1314589f.css

skin-6400f1314589f.css

60 ms

animate.min.css

animate.min.css

66 ms

css

css

42 ms

jquery.min.js

jquery.min.js

82 ms

jquery-migrate.min.js

jquery-migrate.min.js

76 ms

imagesloaded.min.js

imagesloaded.min.js

77 ms

GD-cORe-public.js

GD-cORe-public.js

78 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

80 ms

email-decode.min.js

email-decode.min.js

78 ms

2-layout.js

2-layout.js

135 ms

coblocks-animation.js

coblocks-animation.js

133 ms

tiny-swiper.js

tiny-swiper.js

126 ms

coblocks-tinyswiper-initializer.js

coblocks-tinyswiper-initializer.js

175 ms

jquery.ba-throttle-debounce.min.js

jquery.ba-throttle-debounce.min.js

174 ms

7839785d51d7b0b08fa414e3197230b2-layout-bundle.js

7839785d51d7b0b08fa414e3197230b2-layout-bundle.js

177 ms

jquery.magnificpopup.min.js

jquery.magnificpopup.min.js

176 ms

theme.min.js

theme.min.js

184 ms

scc-c2.min.js

scc-c2.min.js

16 ms

tti.min.js

tti.min.js

96 ms

aadc63d8e8dbd533470bdc4e350bc4af

aadc63d8e8dbd533470bdc4e350bc4af

178 ms

hero-bg.jpg

hero-bg.jpg

176 ms

hero-img-circle.png

hero-img-circle.png

177 ms

rs.png

rs.png

174 ms

whatabr-scaled.jpeg

whatabr-scaled.jpeg

178 ms

1.jpg

1.jpg

173 ms

pic-in-front-of-the-hive-scaled.jpg

pic-in-front-of-the-hive-scaled.jpg

178 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xw.ttf

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xw.ttf

121 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo58a-xw.ttf

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo58a-xw.ttf

123 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58a-xw.ttf

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58a-xw.ttf

149 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

158 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFlOl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFlOl0k30e0.ttf

159 ms

fa-solid-900.woff

fa-solid-900.woff

121 ms

fa-regular-400.woff

fa-regular-400.woff

107 ms

fa-brands-400.woff

fa-brands-400.woff

108 ms

logo.png

logo.png

51 ms

Accessibility Review

whataburger13.com accessibility score

100

Accessibility Issues

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

whataburger13.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

whataburger13.com

Open Graph data is detected on the main page of What A Burger 13. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: