Tools & Wizards About Us
potbellyhogroast.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

potbellyhogroast.com

Page Load Speed

2.4 sec in total

First Response

316 ms

Resources Loaded

1.8 sec

Page Rendered

247 ms

potbellyhogroast.com screenshot

About Website

Click here to check amazing Potbellyhogroast content. Otherwise, check out these important facts you probably never knew about potbellyhogroast.com

Pot Belly Hog Roast is the premier supplier of hog roasts and pig roasts in Nottinghamshire and the East Midlands providing hog roast catering for weddings, parties, corporate events, charity events, ...

Visit potbellyhogroast.com

Key Findings

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

potbellyhogroast.com performance score

0

Network Requests Diagram

potbellyhogroast.com

316 ms

main.css

171 ms

blogstyles.css

172 ms

flickr-revolver.css

174 ms

flickr-revolver-gallery.css

173 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 70% of them (37 requests) were addressed to the original Potbellyhogroast.com, 15% (8 requests) were made to Apis.google.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (846 ms) belongs to the original domain Potbellyhogroast.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 219.2 kB (41%)

Content Size

538.3 kB

After Optimization

319.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Potbellyhogroast.com main page is 538.3 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. 40% of websites need less resources to load. Javascripts take 260.8 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 10.2 kB

  • Original 15.0 kB
  • After minification 14.5 kB
  • After compression 4.8 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 10.2 kB or 68% of the original size.

Image Optimization

-4%

Potential reduce by 9.9 kB

  • Original 251.5 kB
  • After minification 241.6 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. Potbellyhogroast images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 191.3 kB

  • Original 260.8 kB
  • After minification 190.0 kB
  • After compression 69.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 191.3 kB or 73% of the original size.

CSS Optimization

-71%

Potential reduce by 7.9 kB

  • Original 11.0 kB
  • After minification 8.9 kB
  • After compression 3.1 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. Potbellyhogroast.com needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (69%)

Requests Now

51

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

potbellyhogroast.com

potbellyhogroast.com

316 ms

main.css

main.css

171 ms

blogstyles.css

blogstyles.css

172 ms

flickr-revolver.css

flickr-revolver.css

174 ms

flickr-revolver-gallery.css

flickr-revolver-gallery.css

173 ms

fading-headers.css

fading-headers.css

175 ms

count-down.css

count-down.css

175 ms

css

css

22 ms

css

css

34 ms

jquery.js

jquery.js

594 ms

eye.js

eye.js

340 ms

utils.js

utils.js

344 ms

flickr-revolver.js

flickr-revolver.js

342 ms

mootools-1.2.5-core-nc.js

mootools-1.2.5-core-nc.js

602 ms

charactercounter.js

charactercounter.js

345 ms

noobslide.js

noobslide.js

511 ms

fading-headers.js

fading-headers.js

519 ms

validation.js

validation.js

515 ms

count-down.js

count-down.js

514 ms

ga.js

ga.js

26 ms

plusone.js

plusone.js

114 ms

gplus-32.png

gplus-32.png

90 ms

menu-bg-top.gif

menu-bg-top.gif

192 ms

menu.gif

menu.gif

205 ms

menu-bg-foot.gif

menu-bg-foot.gif

219 ms

roast-meat.jpg

roast-meat.jpg

356 ms

pig-in-a-bun.jpg

pig-in-a-bun.jpg

281 ms

roast-pig.jpg

roast-pig.jpg

281 ms

hog_roast.jpg

hog_roast.jpg

424 ms

steak.jpg

steak.jpg

444 ms

main-logo.gif

main-logo.gif

445 ms

sig.gif

sig.gif

450 ms

scroller-icon-1.gif

scroller-icon-1.gif

450 ms

scroller-icon-2.gif

scroller-icon-2.gif

524 ms

scroller-icon-3.gif

scroller-icon-3.gif

593 ms

scroller-icon-4.gif

scroller-icon-4.gif

613 ms

scroller-icon-5.gif

scroller-icon-5.gif

613 ms

where-we-roam.jpg

where-we-roam.jpg

783 ms

pig-roast-machine.jpg

pig-roast-machine.jpg

618 ms

square-facebook.gif

square-facebook.gif

692 ms

square-twitter.gif

square-twitter.gif

761 ms

bg_hog.jpg

bg_hog.jpg

846 ms

2Q-AW1e_taO6pHwMXcXW5w.ttf

2Q-AW1e_taO6pHwMXcXW5w.ttf

57 ms

__utm.gif

__utm.gif

15 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

12 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

11 ms

fastbutton

fastbutton

68 ms

postmessageRelay

postmessageRelay

67 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

23 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

23 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

3 ms

rpc:shindig_random.js

rpc:shindig_random.js

30 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

3 ms

SEO Factors

potbellyhogroast.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 Potbellyhogroast.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 Potbellyhogroast.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

potbellyhogroast.com

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