Tools & Wizards About Us
sanfrancisco.ediblefeast.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

sanfrancisco.ediblefeast.com

Home San Francisco | Edible San Francisco (Archive)

Page Load Speed

2.4 sec in total

First Response

330 ms

Resources Loaded

1.9 sec

Page Rendered

116 ms

sanfrancisco.ediblefeast.com screenshot

About Website

Click here to check amazing San Francisco Edible Feast content for United States. Otherwise, check out these important facts you probably never knew about sanfrancisco.ediblefeast.com

San Francisco's only food magazine. Telling the story of how The City by the Bay eats, drinks and cooks.

Visit sanfrancisco.ediblefeast.com

Key Findings

We analyzed Sanfrancisco.ediblefeast.com page load time and found that the first response time was 330 ms and then it took 2 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. This domain responded with an error, which can significantly jeopardize Sanfrancisco.ediblefeast.com rating and web reputation

Performance Metrics

sanfrancisco.ediblefeast.com performance score

0

Network Requests Diagram

home-san-francisco

330 ms

ados.js

22 ms

acp1cvq.js

43 ms

system.base.css

70 ms

system.menus.css

109 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Sanfrancisco.ediblefeast.com, 13% (13 requests) were made to Use.typekit.net and 3% (3 requests) were made to E-8942.adzerk.net. The less responsive or slowest element that took the longest time to load (437 ms) relates to the external source Admin.ediblecommunities.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (80%)

Content Size

2.3 MB

After Optimization

464.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sanfrancisco.ediblefeast.com main page is 2.3 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. 60% of websites need less resources to load. CSS take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 85.5 kB

  • Original 107.8 kB
  • After minification 106.3 kB
  • After compression 22.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 85.5 kB or 79% of the original size.

Image Optimization

-12%

Potential reduce by 14.6 kB

  • Original 118.1 kB
  • After minification 103.5 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. Obviously, San Francisco Edible Feast needs image optimization as it can save up to 14.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 490.6 kB

  • Original 725.3 kB
  • After minification 561.0 kB
  • After compression 234.7 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 490.6 kB or 68% of the original size.

CSS Optimization

-92%

Potential reduce by 1.2 MB

  • Original 1.3 MB
  • After minification 1.2 MB
  • After compression 104.3 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. Sanfrancisco.ediblefeast.com needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 92% of the original size.

Requests Breakdown

Number of requests can be reduced by 78 (90%)

Requests Now

87

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

home-san-francisco

home-san-francisco

330 ms

ados.js

ados.js

22 ms

acp1cvq.js

acp1cvq.js

43 ms

system.base.css

system.base.css

70 ms

system.menus.css

system.menus.css

109 ms

system.messages.css

system.messages.css

108 ms

system.theme.css

system.theme.css

110 ms

jquery.ui.core.min.css

jquery.ui.core.min.css

110 ms

jquery.ui.theme.min.css

jquery.ui.theme.min.css

138 ms

calendar_multiday.css

calendar_multiday.css

111 ms

date.css

date.css

141 ms

datepicker.1.7.css

datepicker.1.7.css

143 ms

date_repeat_field.css

date_repeat_field.css

144 ms

domain_nav.css

domain_nav.css

141 ms

field.css

field.css

145 ms

logintoboggan.css

logintoboggan.css

173 ms

ados

ados

109 ms

node.css

node.css

150 ms

search.css

search.css

149 ms

user.css

user.css

161 ms

extlink.css

extlink.css

163 ms

views.css

views.css

152 ms

ckeditor.css

ckeditor.css

179 ms

css

css

76 ms

colorbox_style.css

colorbox_style.css

183 ms

ctools.css

ctools.css

181 ms

panels.css

panels.css

185 ms

superfish.css

superfish.css

193 ms

at.layout.css

at.layout.css

195 ms

global.base.css

global.base.css

243 ms

global.styles.css

global.styles.css

437 ms

print.css

print.css

247 ms

edible.default.layout.css

edible.default.layout.css

219 ms

jquery.min.js

jquery.min.js

62 ms

jquery-extend-3.4.0.js

jquery-extend-3.4.0.js

227 ms

jquery-html-prefilter-3.5.0-backport.js

jquery-html-prefilter-3.5.0-backport.js

256 ms

jquery.once.js

jquery.once.js

254 ms

drupal.js

drupal.js

287 ms

jquery-ui.min.js

jquery-ui.min.js

66 ms

jquery.cookie.js

jquery.cookie.js

276 ms

form-single-submit.js

form-single-submit.js

276 ms

extlink.js

extlink.js

284 ms

js

js

83 ms

sharethis.js

sharethis.js

60 ms

mc-validate.js

mc-validate.js

79 ms

jRespond.min.js

jRespond.min.js

292 ms

tooltip.js

tooltip.js

276 ms

jquery.atooltip.min.js

jquery.atooltip.min.js

237 ms

jquery.dropkick-1.0.0.js

jquery.dropkick-1.0.0.js

247 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

243 ms

colorbox.js

colorbox.js

255 ms

colorbox_style.js

colorbox_style.js

268 ms

colorbox_load.js

colorbox_load.js

239 ms

colorbox_inline.js

colorbox_inline.js

243 ms

googleanalytics.js

googleanalytics.js

248 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

254 ms

supposition.js

supposition.js

270 ms

superfish.js

superfish.js

269 ms

supersubs.js

supersubs.js

243 ms

superfish.js

superfish.js

246 ms

equalHeight.js

equalHeight.js

255 ms

idangerous.swiper.js

idangerous.swiper.js

396 ms

jquery.jlabel.js

jquery.jlabel.js

261 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

261 ms

jquery.kinetic.min.js

jquery.kinetic.min.js

247 ms

jquery.smoothdivscroll-1.3-min.js

jquery.smoothdivscroll-1.3-min.js

366 ms

modernizr.min.js

modernizr.min.js

364 ms

st_misc.js

st_misc.js

363 ms

eddy_vote.js

eddy_vote.js

352 ms

st_panels_dropdown_title.js

st_panels_dropdown_title.js

352 ms

custom.js

custom.js

327 ms

jquery.flexslider.js

jquery.flexslider.js

319 ms

custom.js

custom.js

302 ms

jquery.sticky.js

jquery.sticky.js

299 ms

slick.min.js

slick.min.js

293 ms

navigation.js

navigation.js

291 ms

readmore.min.js

readmore.min.js

271 ms

custom.js

custom.js

270 ms

custom_new.js

custom_new.js

262 ms

home.js

home.js

261 ms

ingredients.js

ingredients.js

304 ms

icons-s8ac35b3cf0.png

icons-s8ac35b3cf0.png

61 ms

logo.png

logo.png

61 ms

Edible-Communities-Footer.png

Edible-Communities-Footer.png

62 ms

3df34360f1c04059bf71776f6643221a.jpg

3df34360f1c04059bf71776f6643221a.jpg

357 ms

i.gif

i.gif

346 ms

37047d3f5e804bfcad8f194577b402c2.png

37047d3f5e804bfcad8f194577b402c2.png

15 ms

i.gif

i.gif

11 ms

d

d

10 ms

d

d

30 ms

d

d

26 ms

d

d

25 ms

d

d

27 ms

d

d

26 ms

d

d

25 ms

d

d

27 ms

d

d

58 ms

d

d

28 ms

d

d

27 ms

d

d

28 ms

SEO Factors

sanfrancisco.ediblefeast.com SEO score

0

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 Sanfrancisco.ediblefeast.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 Sanfrancisco.ediblefeast.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

sanfrancisco.ediblefeast.com

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