Tools & Wizards About Us

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

foodnext.net

食力foodNEXT‧食事求實的知識頻道

Page Load Speed

8.7 sec in total

First Response

39 ms

Resources Loaded

8 sec

Page Rendered

670 ms

About Website

Visit foodnext.net now to see the best up-to-date Foodnext content for Taiwan and also check out these interesting facts you probably never knew about foodnext.net

《食力foodNEXT》一家獨立運營的媒體，以食為本，站在飲食產業第一線，從國內外最新產業動態、飲食美學與文化、科學客觀的知識剖析、深入的報導與專題製作，提供讀者完整全面的產業報導，讓關注食事的閱聽眾，開啟食域新觀點。讀者閱讀完食力官網文章、回答「食力學堂」獲取學分後，還能用學分兌換多款飲食新品，分享試用心得，在全台最專業的飲食媒體和最大食品試吃平台，為推動飲食產業的創新貢獻一份心力！

Visit foodnext.net

Key Findings

We analyzed Foodnext.net page load time and found that the first response time was 39 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

foodnext.net performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value1,930 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.793

5/100

15%

TTI (Time to Interactive)

Value25.7 s

0/100

10%

Network Requests Diagram

foodnext.net

39 ms

foodnext.net

473 ms

www.foodnext.net

3538 ms

bootstrap.min.css

23 ms

fontawesome.min.css

29 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 61% of them (70 requests) were addressed to the original Foodnext.net, 7% (8 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to . The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Foodnext.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 848.1 kB (14%)

Content Size

6.0 MB

After Optimization

5.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foodnext.net main page is 6.0 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. Only a small number of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 134.0 kB

  • Original 167.4 kB
  • After minification 139.4 kB
  • After compression 33.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. This page needs HTML code to be minified as it can gain 28.0 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 134.0 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 106.0 kB

  • Original 4.1 MB
  • After minification 4.0 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. Foodnext images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 503.9 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 910.4 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 503.9 kB or 36% of the original size.

CSS Optimization

-32%

Potential reduce by 104.3 kB

  • Original 323.2 kB
  • After minification 321.2 kB
  • After compression 219.0 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. Foodnext.net needs all CSS files to be minified and compressed as it can save up to 104.3 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (56%)

Requests Now

98

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

foodnext.net accessibility score

66

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

foodnext.net 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

High

Page has valid source maps

SEO Factors

foodnext.net SEO score

84

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

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

    JA

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foodnext.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Foodnext.net 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 description is not detected on the main page of Foodnext. 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: