Tools & Wizards About Us
potbelly.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

potbelly.com

Page Load Speed

24.4 sec in total

First Response

10.8 sec

Resources Loaded

11.9 sec

Page Rendered

1.7 sec

potbelly.com screenshot

About Website

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

Enjoy all the good vibes and great sandwiches at a Potbelly Sandwich Shop near you today.

Visit potbelly.com

Key Findings

We analyzed Potbelly.com page load time and found that the first response time was 10.8 sec and then it took 13.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

potbelly.com performance score

0

Network Requests Diagram

potbelly.com

10753 ms

css

75 ms

fonts.css

114 ms

common.css

77 ms

common-noscroll.css

78 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 19% of them (15 requests) were addressed to the original Potbelly.com, 46% (36 requests) were made to Cdn.potbelly.com and 8% (6 requests) were made to Px.owneriq.net. The less responsive or slowest element that took the longest time to load (10.8 sec) belongs to the original domain Potbelly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 439.5 kB (22%)

Content Size

2.0 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 27.3 kB

  • Original 36.8 kB
  • After minification 28.9 kB
  • After compression 9.5 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 7.9 kB, which is 21% 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 27.3 kB or 74% of the original size.

Image Optimization

-4%

Potential reduce by 63.6 kB

  • Original 1.5 MB
  • After minification 1.4 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. Potbelly images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 260.1 kB

  • Original 389.5 kB
  • After minification 373.6 kB
  • After compression 129.4 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 260.1 kB or 67% of the original size.

CSS Optimization

-91%

Potential reduce by 88.5 kB

  • Original 97.7 kB
  • After minification 51.1 kB
  • After compression 9.2 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. Potbelly.com needs all CSS files to be minified and compressed as it can save up to 88.5 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (47%)

Requests Now

68

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

potbelly.com

potbelly.com

10753 ms

css

css

75 ms

fonts.css

fonts.css

114 ms

common.css

common.css

77 ms

common-noscroll.css

common-noscroll.css

78 ms

home.css

home.css

110 ms

jquery-1.6.2.min.js

jquery-1.6.2.min.js

88 ms

basic-jquery-slider.js

basic-jquery-slider.js

84 ms

WebResource.axd

WebResource.axd

262 ms

ScriptResource.axd

ScriptResource.axd

341 ms

ScriptResource.axd

ScriptResource.axd

318 ms

mmConversionTagV4.js

mmConversionTagV4.js

42 ms

ScriptResource.axd

ScriptResource.axd

250 ms

ScriptResource.axd

ScriptResource.axd

268 ms

ScriptResource.axd

ScriptResource.axd

269 ms

ScriptResource.axd

ScriptResource.axd

275 ms

ScriptResource.axd

ScriptResource.axd

295 ms

ScriptResource.axd

ScriptResource.axd

297 ms

ScriptResource.axd

ScriptResource.axd

297 ms

ScriptResource.axd

ScriptResource.axd

606 ms

dc.js

dc.js

197 ms

Potbly.js

Potbly.js

182 ms

background_10b.jpg

background_10b.jpg

123 ms

beacon

beacon

227 ms

logo_header.png

logo_header.png

167 ms

skinnyMonte-headline.png

skinnyMonte-headline.png

169 ms

skinnyMonte-3card.png

skinnyMonte-3card.png

167 ms

close_20.png

close_20.png

167 ms

SkinnyMonte_Rotator.jpg

SkinnyMonte_Rotator.jpg

165 ms

MacCheese_Rotator.jpg

MacCheese_Rotator.jpg

164 ms

App_rotator.jpg

App_rotator.jpg

164 ms

orderOnline_10.png

orderOnline_10.png

196 ms

music_homepage.png

music_homepage.png

195 ms

fundraiser_homepage.png

fundraiser_homepage.png

196 ms

consumerpick_homepage.png

consumerpick_homepage.png

195 ms

tripadivsor_homepage.png

tripadivsor_homepage.png

196 ms

btn_orderOnline.png

btn_orderOnline.png

129 ms

144 ms

__utm.gif

__utm.gif

45 ms

orderOnline_arrow.png

orderOnline_arrow.png

43 ms

bg_mainmenu.png

bg_mainmenu.png

34 ms

menu_menu.png

menu_menu.png

33 ms

menu_catering.png

menu_catering.png

33 ms

menu_ourpromise.png

menu_ourpromise.png

32 ms

menu_ourstory.png

menu_ourstory.png

33 ms

menu_corprespons.png

menu_corprespons.png

32 ms

menu_shoplocator.png

menu_shoplocator.png

32 ms

yRJpjT39KxACO9F31mj_LsevLjdB67LO9Bn4JiESQyE.ttf

yRJpjT39KxACO9F31mj_LsevLjdB67LO9Bn4JiESQyE.ttf

71 ms

ep

ep

66 ms

appnexus

appnexus

49 ms

ActivityServer.bs

ActivityServer.bs

44 ms

ecc

ecc

55 ms

spp.pl

spp.pl

334 ms

trackconversion

trackconversion

180 ms

fbds.js

fbds.js

321 ms

oct.js

oct.js

71 ms

adsct

adsct

313 ms

adsct

adsct

243 ms

skinnyMonte-bg.png

skinnyMonte-bg.png

83 ms

cups.png

cups.png

61 ms

btn_veteran_10.png

btn_veteran_10.png

61 ms

btn_rookie_10.png

btn_rookie_10.png

51 ms

ico_fb.png

ico_fb.png

59 ms

ico_tw.png

ico_tw.png

61 ms

ico_gm.png

ico_gm.png

62 ms

ico_ttu.png

ico_ttu.png

62 ms

signpainter-regular-webfont.ttf

signpainter-regular-webfont.ttf

271 ms

generic

generic

41 ms

fp.js

fp.js

259 ms

pixel

pixel

180 ms

quant.js

quant.js

146 ms

underline_10.gif

underline_10.gif

150 ms

btn_homeRotator.png

btn_homeRotator.png

96 ms

cm

cm

83 ms

pixel;r=1945721961;a=p-B6zYfhc47YaE1;labels=_fp.event.Homepage;fpan=1;fpa=P0-1132603621-1455664242897;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1455664242893;tzo=-180;ref=;url=http%3A%2F%2Fpotbelly.com%2F;ogl=

pixel;r=1945721961;a=p-B6zYfhc47YaE1;labels=_fp.event.Homepage;fpan=1;fpa=P0-1132603621-1455664242897;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1455664242893;tzo=-180;ref=;url=http%3A%2F%2Fpotbelly.com%2F;ogl=

47 ms

106 ms

generic

generic

37 ms

offsite_event.php

offsite_event.php

81 ms

ermcm

ermcm

13 ms

SEO Factors

potbelly.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Potbelly.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Potbelly.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

potbelly.com

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