Tools & Wizards About Us
36food.com screenshot

Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 44

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

36food.com

食品招聘网 食品招聘网－专业食品人才网站,这里是全国食品人才集中的网站,专业食品人才突破20万！

Page Load Speed

26.4 sec in total

First Response

2.1 sec

Resources Loaded

24.2 sec

Page Rendered

134 ms

36food.com screenshot

About Website

Visit 36food.com now to see the best up-to-date 36 Food content and also check out these interesting facts you probably never knew about 36food.com

食品招聘网！

Visit 36food.com

Key Findings

We analyzed 36food.com page load time and found that the first response time was 2.1 sec and then it took 24.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 19 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

36food.com performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value4.2 s

85/100

10%

Network Requests Diagram

36food.com

2113 ms

common.css

2594 ms

callingtbl.css

1465 ms

jquery.min.js

3463 ms

common.js

996 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 46% of them (26 requests) were addressed to the original 36food.com, 45% (25 requests) were made to Ad.36.cn and 7% (4 requests) were made to Old.36.cn. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Ad.36.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 75.7 kB (79%)

Content Size

95.9 kB

After Optimization

20.2 kB

  • HTML
  • JavaScript

In fact, the total size of 36food.com main page is 95.9 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. Only 10% of websites need less resources to load. HTML takes 83.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 68.0 kB

  • Original 83.4 kB
  • After minification 77.1 kB
  • After compression 15.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 68.0 kB or 82% of the original size.

JavaScript Optimization

-62%

Potential reduce by 7.8 kB

  • Original 12.5 kB
  • After minification 12.5 kB
  • After compression 4.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 7.8 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (36%)

Requests Now

25

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

36food.com

36food.com

2113 ms

common.css

common.css

2594 ms

callingtbl.css

callingtbl.css

1465 ms

jquery.min.js

jquery.min.js

3463 ms

common.js

common.js

996 ms

citySingleSelector.js

citySingleSelector.js

1259 ms

jobSelectorToIndex.js

jobSelectorToIndex.js

2232 ms

ip_win.js

ip_win.js

1892 ms

tip.js

tip.js

1807 ms

stats

stats

226 ms

545923.gif

545923.gif

1990 ms

776531.gif

776531.gif

1345 ms

545896%20(1).gif

545896%20(1).gif

1342 ms

773339.gif

773339.gif

1355 ms

545935.gif

545935.gif

1335 ms

544951.gif

544951.gif

1354 ms

543532.gif

543532.gif

19811 ms

545898.gif

545898.gif

19811 ms

545906.gif

545906.gif

19811 ms

new_1.gif

new_1.gif

19811 ms

543328.gif

543328.gif

19811 ms

545930.gif

545930.gif

19811 ms

545907.gif

545907.gif

19811 ms

545822.gif

545822.gif

19810 ms

545861.gif

545861.gif

19810 ms

545849.gif

545849.gif

19811 ms

6882.gif

6882.gif

19811 ms

545882.gif

545882.gif

19810 ms

545908.gif

545908.gif

19810 ms

545918.gif

545918.gif

19810 ms

545928.gif

545928.gif

19810 ms

545926.gif

545926.gif

19810 ms

545914.gif

545914.gif

19810 ms

545919.gif

545919.gif

19810 ms

545845.gif

545845.gif

19810 ms

778301.gif

778301.gif

507 ms

wangan.gif

wangan.gif

256 ms

jjcc2.gif

jjcc2.gif

257 ms

andBarcode.png

andBarcode.png

486 ms

global_x.png

global_x.png

513 ms

mobile_app_dw_btn.gif

mobile_app_dw_btn.gif

940 ms

global.png

global.png

1004 ms

36food_logo.gif

36food_logo.gif

479 ms

iosBarcode.png

iosBarcode.png

943 ms

appic.png

appic.png

965 ms

nav.png

nav.png

472 ms

chs_p_bg.png

chs_p_bg.png

968 ms

login_icons.png

login_icons.png

969 ms

chs_e_bg.png

chs_e_bg.png

963 ms

hotline_ico.png

hotline_ico.png

751 ms

hotBg.jpg

hotBg.jpg

1184 ms

dot.gif

dot.gif

1180 ms

ft_contact.png

ft_contact.png

1207 ms

ft_report_err_btn.png

ft_report_err_btn.png

1207 ms

citydata.json

citydata.json

1251 ms

backtop.png

backtop.png

499 ms

Accessibility Review

36food.com accessibility score

44

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

36food.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

36food.com SEO score

62

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 36food.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 36food.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

36food.com

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