Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

cooksocial.org

Welcome to nginx!

Page Load Speed

11.6 sec in total

First Response

479 ms

Resources Loaded

10.7 sec

Page Rendered

392 ms

cooksocial.org screenshot

About Website

Click here to check amazing Cooksocial content for United States. Otherwise, check out these important facts you probably never knew about cooksocial.org

On Cooksocial we provide a network for social cooking and eating, encourage cooking as elemental heritage and connect people. Get part of it free!

Visit cooksocial.org

Key Findings

We analyzed Cooksocial.org page load time and found that the first response time was 479 ms and then it took 11.1 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

cooksocial.org performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.7 s

100/100

25%

SI (Speed Index)

Value0.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.7 s

100/100

10%

Network Requests Diagram

cooksocial.org

479 ms

4698 ms

css

62 ms

app.css

258 ms

default.css

377 ms

Our browser made a total of 140 requests to load all elements on the main page. We found that 49% of them (68 requests) were addressed to the original Cooksocial.org, 19% (26 requests) were made to Maps.google.com and 8% (11 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Cooksocial.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (55%)

Content Size

3.9 MB

After Optimization

1.8 MB

In fact, the total size of Cooksocial.org main page is 3.9 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. Javascripts take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 61.2 kB

  • Original 76.1 kB
  • After minification 73.3 kB
  • After compression 14.9 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 61.2 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 53.3 kB

  • Original 1.2 MB
  • After minification 1.2 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. Cooksocial images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 1.5 MB

  • Original 2.0 MB
  • After minification 1.6 MB
  • After compression 483.3 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 1.5 MB or 76% of the original size.

CSS Optimization

-88%

Potential reduce by 570.7 kB

  • Original 646.8 kB
  • After minification 436.9 kB
  • After compression 76.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. Cooksocial.org needs all CSS files to be minified and compressed as it can save up to 570.7 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 68 (52%)

Requests Now

132

After Optimization

64

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

Accessibility Review

cooksocial.org accessibility score

89

Accessibility Issues

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

cooksocial.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

cooksocial.org SEO score

64

Search Engine Optimization Advices

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 Cooksocial.org 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 Cooksocial.org 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 Cooksocial. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: