Tools & Wizards About Us
foodpair.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

foodpair.com

FoodPair | Recipe Search Engine - Search by Ingredient, Site and Diet

Page Load Speed

1.4 sec in total

First Response

300 ms

Resources Loaded

897 ms

Page Rendered

239 ms

foodpair.com screenshot

About Website

Click here to check amazing Food Pair content. Otherwise, check out these important facts you probably never knew about foodpair.com

FoodPair is a recipe search engine that makes it easy for you to find recipes with ingredients you have. Search nearly a million recipes by ingredient, diet, course and site.

Visit foodpair.com

Key Findings

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

Performance Metrics

foodpair.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.343

32/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

foodpair.com

300 ms

base_packaged.css

266 ms

css

21 ms

like.php

138 ms

2012_07_18-PestoTart-1.jpg

82 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 27% of them (15 requests) were addressed to the original Foodpair.com, 55% (30 requests) were made to S3.amazonaws.com and 5% (3 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (401 ms) belongs to the original domain Foodpair.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 272.0 kB (24%)

Content Size

1.1 MB

After Optimization

871.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foodpair.com main page is 1.1 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 767.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 36.9 kB

  • Original 44.3 kB
  • After minification 40.6 kB
  • After compression 7.4 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 36.9 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 6.3 kB

  • Original 767.6 kB
  • After minification 761.3 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. Food Pair images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 167.4 kB

  • Original 257.1 kB
  • After minification 257.1 kB
  • After compression 89.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 167.4 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 61.4 kB

  • Original 74.1 kB
  • After minification 68.1 kB
  • After compression 12.8 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. Foodpair.com needs all CSS files to be minified and compressed as it can save up to 61.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (16%)

Requests Now

50

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

foodpair.com

foodpair.com

300 ms

base_packaged.css

base_packaged.css

266 ms

css

css

21 ms

like.php

like.php

138 ms

2012_07_18-PestoTart-1.jpg

2012_07_18-PestoTart-1.jpg

82 ms

application_packaged.js

application_packaged.js

401 ms

log.js

log.js

22 ms

CCC_-_1-26-2012_-_Sweet_Potato_Carrot_Soup.jpg

CCC_-_1-26-2012_-_Sweet_Potato_Carrot_Soup.jpg

42 ms

tm1b02_greek_meatballs_lg.jpg

tm1b02_greek_meatballs_lg.jpg

42 ms

recipe_331_lg.jpg

recipe_331_lg.jpg

50 ms

recipe-119.jpg

recipe-119.jpg

59 ms

fall-salad.jpg

fall-salad.jpg

111 ms

tuna-sandwich-rs-1225417-l.jpg

tuna-sandwich-rs-1225417-l.jpg

75 ms

glazed-salmon-ck-223078-l.jpg

glazed-salmon-ck-223078-l.jpg

75 ms

chkn-fricassee-hl-1559145-l.jpg

chkn-fricassee-hl-1559145-l.jpg

107 ms

2494082872_dd3c7e4014.jpg

2494082872_dd3c7e4014.jpg

100 ms

WS0206_Chocolate-Caramel-Pumpkin-Cupcakes_s4x3_lg.jpg

WS0206_Chocolate-Caramel-Pumpkin-Cupcakes_s4x3_lg.jpg

107 ms

102948.jpg

102948.jpg

106 ms

recipe-4025.jpg

recipe-4025.jpg

128 ms

Orzo_with_Toasted_Pine_Nuts.JPGsmaller.jpg

Orzo_with_Toasted_Pine_Nuts.JPGsmaller.jpg

128 ms

45_nine_col.jpg

45_nine_col.jpg

136 ms

recipe-1513.jpg

recipe-1513.jpg

149 ms

img3l.jpg

img3l.jpg

132 ms

barnsley_chops_with_60141_16x9.jpg

barnsley_chops_with_60141_16x9.jpg

163 ms

recipe-10567.jpg

recipe-10567.jpg

168 ms

dt-spicyspaghetti.jpg

dt-spicyspaghetti.jpg

142 ms

104494.jpg

104494.jpg

184 ms

fried-chicken-ck-1536720-l.jpg

fried-chicken-ck-1536720-l.jpg

166 ms

2824824445_62c429c164.jpg

2824824445_62c429c164.jpg

171 ms

sacklunch.jpg

sacklunch.jpg

176 ms

IMG_5688.JPG

IMG_5688.JPG

227 ms

2009_02_18-Salad.jpg

2009_02_18-Salad.jpg

227 ms

beet-soup-ck-1120314-l.jpg

beet-soup-ck-1120314-l.jpg

228 ms

salmon-relish-ck-1041925-l.jpg

salmon-relish-ck-1041925-l.jpg

227 ms

1008762920_18a8a5347f.jpg

1008762920_18a8a5347f.jpg

227 ms

intensechocolatecook_87336_16x9.jpg

intensechocolatecook_87336_16x9.jpg

291 ms

scroll-top.png

scroll-top.png

136 ms

load-scroll-dark.gif

load-scroll-dark.gif

138 ms

TttXWwYVW0v.js

TttXWwYVW0v.js

38 ms

FEppCFCt76d.png

FEppCFCt76d.png

16 ms

TttXWwYVW0v.js

TttXWwYVW0v.js

9 ms

html-bg.png

html-bg.png

69 ms

sprite.png

sprite.png

302 ms

sticky-nav-bg.png

sticky-nav-bg.png

68 ms

bg-nav-item.png

bg-nav-item.png

136 ms

green-btn-bg.png

green-btn-bg.png

135 ms

bg-featured.png

bg-featured.png

136 ms

helveticaltstd-bold-webfont.woff

helveticaltstd-bold-webfont.woff

238 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

6 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

16 ms

ga.js

ga.js

37 ms

autocomplete

autocomplete

78 ms

loadingAnimation.gif

loadingAnimation.gif

131 ms

load-scroll.gif

load-scroll.gif

129 ms

__utm.gif

__utm.gif

91 ms

Accessibility Review

foodpair.com accessibility score

84

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

foodpair.com best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

foodpair.com SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foodpair.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Foodpair.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

foodpair.com

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