Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

epicurious.com

Epicurious – Recipes, Menu Ideas, Videos & Cooking Tips | Epicurious

Page Load Speed

86.6 sec in total

First Response

1.8 sec

Resources Loaded

62.5 sec

Page Rendered

22.2 sec

epicurious.com screenshot

About Website

Visit epicurious.com now to see the best up-to-date Epicurious content for United States and also check out these interesting facts you probably never knew about epicurious.com

Since 1995, Epicurious has been the ultimate food resource for the home cook, with daily kitchen tips, fun cooking videos, and, oh yeah, over 33,000 recipes.

Visit epicurious.com

Key Findings

We analyzed Epicurious.com page load time and found that the first response time was 1.8 sec and then it took 84.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 20 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

epicurious.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value17.4 s

0/100

10%

TBT (Total Blocking Time)

Value20,400 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.057

98/100

15%

TTI (Time to Interactive)

Value42.9 s

0/100

10%

Network Requests Diagram

www.epicurious.com

1829 ms

zpl6zji.js

5414 ms

satelliteLib-b8937e0c536ed51fe92efb5ca25fc6f76fdeef0e.js

3878 ms

services.min.js

2741 ms

24-BokChoy.jpg

4804 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 15% of them (13 requests) were addressed to the original Epicurious.com, 11% (10 requests) were made to Use.typekit.net and 9% (8 requests) were made to Assets.epicurious.com. The less responsive or slowest element that took the longest time to load (23.1 sec) relates to the external source Google-analytics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.2 MB (45%)

Content Size

9.3 MB

After Optimization

5.1 MB

In fact, the total size of Epicurious.com main page is 9.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 5.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 195.0 kB

  • Original 243.6 kB
  • After minification 240.2 kB
  • After compression 48.6 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 195.0 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 69.3 kB

  • Original 3.5 MB
  • After minification 3.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. Epicurious images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 3.6 MB

  • Original 5.1 MB
  • After minification 5.0 MB
  • After compression 1.6 MB

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 3.6 MB or 70% of the original size.

CSS Optimization

-82%

Potential reduce by 350.1 kB

  • Original 425.9 kB
  • After minification 379.3 kB
  • After compression 75.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. Epicurious.com needs all CSS files to be minified and compressed as it can save up to 350.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (59%)

Requests Now

51

After Optimization

21

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

Accessibility Review

epicurious.com accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

epicurious.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

epicurious.com SEO score

92

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

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

High

Tap targets are not sized appropriately

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

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