Tools & Wizards About Us
foodnext.net screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 65

    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
    53% of websites

foodnext.net

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

Page Load Speed

15.6 sec in total

First Response

1.9 sec

Resources Loaded

12.8 sec

Page Rendered

949 ms

foodnext.net screenshot

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 1.9 sec and then it took 13.7 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

foodnext.net performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value1,390 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.793

5/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

foodnext.net

1930 ms

bootstrap.min.css

1210 ms

jquery.bxslider.css

408 ms

owl.carousel.min.css

411 ms

jquery.fancybox.css

421 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (28%)

Content Size

3.7 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foodnext.net main page is 3.7 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. 80% 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. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 120.6 kB

  • Original 140.6 kB
  • After minification 99.0 kB
  • After compression 20.0 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 41.6 kB, which is 30% 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 120.6 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 98.9 kB

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

JavaScript Optimization

-59%

Potential reduce by 360.4 kB

  • Original 614.6 kB
  • After minification 551.7 kB
  • After compression 254.2 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 360.4 kB or 59% of the original size.

CSS Optimization

-73%

Potential reduce by 474.2 kB

  • Original 645.8 kB
  • After minification 572.0 kB
  • After compression 171.6 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 474.2 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (23%)

Requests Now

184

After Optimization

142

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 184 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 28 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

foodnext.net

foodnext.net

1930 ms

bootstrap.min.css

bootstrap.min.css

1210 ms

jquery.bxslider.css

jquery.bxslider.css

408 ms

owl.carousel.min.css

owl.carousel.min.css

411 ms

jquery.fancybox.css

jquery.fancybox.css

421 ms

kyart.css

kyart.css

1295 ms

kyart_rs.css

kyart_rs.css

810 ms

theme.css

theme.css

612 ms

modernizr-2.6.2-respond-1.1.0.min.js

modernizr-2.6.2-respond-1.1.0.min.js

833 ms

connect.js

connect.js

817 ms

adsbygoogle.js

adsbygoogle.js

6 ms

jquery.min.js

jquery.min.js

84 ms

jquery.min.js

jquery.min.js

416 ms

jquery-migrate.min.js

jquery-migrate.min.js

208 ms

bootstrap.min.js

bootstrap.min.js

204 ms

bootstrap-tabdrop.js

bootstrap-tabdrop.js

211 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

390 ms

jquery.imagesloaded.min.js

jquery.imagesloaded.min.js

405 ms

jquery-imagefill.js

jquery-imagefill.js

414 ms

lazysizes.min.js

lazysizes.min.js

419 ms

owl.carousel.min.js

owl.carousel.min.js

489 ms

jquery.fancybox.js

jquery.fancybox.js

592 ms

core.js

core.js

1010 ms

canboo.js

canboo.js

620 ms

cht-accordion-menu.js

cht-accordion-menu.js

619 ms

jquery.shuffle.min.js

jquery.shuffle.min.js

628 ms

ui_setting.js

ui_setting.js

704 ms

kyart-ui.css

kyart-ui.css

1127 ms

style.css

style.css

210 ms

css

css

23 ms

font-awesome.min.css

font-awesome.min.css

228 ms

atrk.js

atrk.js

592 ms

sdk.js

sdk.js

593 ms

analytics.js

analytics.js

339 ms

menu.png

menu.png

551 ms

logo.png

logo.png

551 ms

GetImg.aspx

GetImg.aspx

1787 ms

GetImg.aspx

GetImg.aspx

3062 ms

GetImg.aspx

GetImg.aspx

552 ms

GetImg.aspx

GetImg.aspx

1716 ms

GetImg.aspx

GetImg.aspx

1006 ms

GetImg.aspx

GetImg.aspx

1716 ms

GetImg.aspx

GetImg.aspx

1006 ms

GetImg.aspx

GetImg.aspx

2068 ms

GetImg.aspx

GetImg.aspx

2548 ms

GetImg.aspx

GetImg.aspx

1785 ms

GetImg.aspx

GetImg.aspx

2061 ms

GetImg.aspx

GetImg.aspx

1988 ms

GetImg.aspx

GetImg.aspx

2497 ms

GetImg.aspx

GetImg.aspx

2207 ms

GetImg.aspx

GetImg.aspx

2256 ms

GetImg.aspx

GetImg.aspx

2264 ms

GetImg.aspx

GetImg.aspx

2421 ms

GetImg.aspx

GetImg.aspx

2477 ms

GetImg.aspx

GetImg.aspx

2996 ms

GetImg.aspx

GetImg.aspx

2639 ms

GetImg.aspx

GetImg.aspx

2697 ms

GetImg.aspx

GetImg.aspx

2720 ms

GetImg.aspx

GetImg.aspx

2754 ms

GetImg.aspx

GetImg.aspx

2856 ms

GetImg.aspx

GetImg.aspx

2923 ms

GetImg.aspx

GetImg.aspx

2948 ms

GetImg.aspx

GetImg.aspx

2967 ms

GetImg.aspx

GetImg.aspx

3076 ms

GetImg.aspx

GetImg.aspx

3146 ms

GetImg.aspx

GetImg.aspx

3177 ms

GetImg.aspx

GetImg.aspx

3183 ms

GetImg.aspx

GetImg.aspx

3213 ms

GetImg.aspx

GetImg.aspx

3272 ms

GetImg.aspx

GetImg.aspx

3004 ms

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

32 ms

DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf

DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf

33 ms

MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf

MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf

28 ms

k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf

k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf

27 ms

xjAJXh38I15wypJXxuGMBiwlidHJgAgmTjOEEzwu1L8.ttf

xjAJXh38I15wypJXxuGMBiwlidHJgAgmTjOEEzwu1L8.ttf

25 ms

PRmiXeptR36kaC0GEAetxt6Naowg1QhaIq8kLGtQSos.ttf

PRmiXeptR36kaC0GEAetxt6Naowg1QhaIq8kLGtQSos.ttf

25 ms

PRmiXeptR36kaC0GEAetxs1QGe9x6ME_FQCWJB3n6z8.ttf

PRmiXeptR36kaC0GEAetxs1QGe9x6ME_FQCWJB3n6z8.ttf

28 ms

PRmiXeptR36kaC0GEAetxjdGNerWpg2Hn6A-BxWgZ_I.ttf

PRmiXeptR36kaC0GEAetxjdGNerWpg2Hn6A-BxWgZ_I.ttf

27 ms

uGnhz0efzj5L2mcR2c=

uGnhz0efzj5L2mcR2c=

16 ms

hNUNU3K

hNUNU3K

18 ms

js0KdQVdLntIwjz0C4YFnxFZ+CzQUrHPB621L0pWyGFi6KIvvMUx3N778EPBFH08PUP4TAA9Ntg==

js0KdQVdLntIwjz0C4YFnxFZ+CzQUrHPB621L0pWyGFi6KIvvMUx3N778EPBFH08PUP4TAA9Ntg==

17 ms

BcWxkdT

BcWxkdT

16 ms

collect

collect

78 ms

iconfont.svg

iconfont.svg

4487 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

3068 ms

atrk.gif

atrk.gif

122 ms

collect

collect

1095 ms

test.png

test.png

1096 ms

GetImg.aspx

GetImg.aspx

2789 ms

ca-pub-7541759169175083.js

ca-pub-7541759169175083.js

384 ms

zrt_lookup.html

zrt_lookup.html

1071 ms

show_ads_impl.js

show_ads_impl.js

356 ms

1109 ms

GetImg.aspx

GetImg.aspx

2434 ms

GetImg.aspx

GetImg.aspx

2486 ms

ads

ads

493 ms

xd_arbiter.php

xd_arbiter.php

639 ms

xd_arbiter.php

xd_arbiter.php

888 ms

GetImg.aspx

GetImg.aspx

1801 ms

GetImg.aspx

GetImg.aspx

1955 ms

osd.js

osd.js

39 ms

m_js_controller.js

m_js_controller.js

83 ms

abg.js

abg.js

100 ms

GetImg.aspx

GetImg.aspx

1891 ms

GetImg.aspx

GetImg.aspx

2000 ms

favicon

favicon

114 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

113 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

95 ms

s

s

79 ms

x_button_blue2.png

x_button_blue2.png

62 ms

GetImg.aspx

GetImg.aspx

1802 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

9 ms

GetImg.aspx

GetImg.aspx

1782 ms

GetImg.aspx

GetImg.aspx

1779 ms

GetImg.aspx

GetImg.aspx

1668 ms

GetImg.aspx

GetImg.aspx

1667 ms

GetImg.aspx

GetImg.aspx

1688 ms

GetImg.aspx

GetImg.aspx

1656 ms

GetImg.aspx

GetImg.aspx

2109 ms

GetImg.aspx

GetImg.aspx

1598 ms

GetImg.aspx

GetImg.aspx

1595 ms

GetImg.aspx

GetImg.aspx

1533 ms

GetImg.aspx

GetImg.aspx

1614 ms

GetImg.aspx

GetImg.aspx

2101 ms

GetImg.aspx

GetImg.aspx

1601 ms

GetImg.aspx

GetImg.aspx

1537 ms

GetImg.aspx

GetImg.aspx

1616 ms

GetImg.aspx

GetImg.aspx

1624 ms

GetImg.aspx

GetImg.aspx

1644 ms

GetImg.aspx

GetImg.aspx

1778 ms

GetImg.aspx

GetImg.aspx

1732 ms

GetImg.aspx

GetImg.aspx

2232 ms

GetImg.aspx

GetImg.aspx

2198 ms

GetImg.aspx

GetImg.aspx

1824 ms

GetImg.aspx

GetImg.aspx

1819 ms

GetImg.aspx

GetImg.aspx

1864 ms

GetImg.aspx

GetImg.aspx

1960 ms

GetImg.aspx

GetImg.aspx

2463 ms

GetImg.aspx

GetImg.aspx

1855 ms

GetImg.aspx

GetImg.aspx

2853 ms

GetImg.aspx

GetImg.aspx

1977 ms

GetImg.aspx

GetImg.aspx

1975 ms

GetImg.aspx

GetImg.aspx

1857 ms

GetImg.aspx

GetImg.aspx

1890 ms

GetImg.aspx

GetImg.aspx

1913 ms

GetImg.aspx

GetImg.aspx

1920 ms

GetImg.aspx

GetImg.aspx

1954 ms

GetImg.aspx

GetImg.aspx

1933 ms

GetImg.aspx

GetImg.aspx

2328 ms

border-white.png

border-white.png

2086 ms

GetImg.aspx

GetImg.aspx

2241 ms

GetImg.aspx

GetImg.aspx

2945 ms

GetImg.aspx

GetImg.aspx

2955 ms

GetImg.aspx

GetImg.aspx

2139 ms

GetImg.aspx

GetImg.aspx

2446 ms

GetImg.aspx

GetImg.aspx

2460 ms

GetImg.aspx

GetImg.aspx

2635 ms

GetImg.aspx

GetImg.aspx

2363 ms

GetImg.aspx

GetImg.aspx

2418 ms

GetImg.aspx

GetImg.aspx

2334 ms

GetImg.aspx

GetImg.aspx

3399 ms

GetImg.aspx

GetImg.aspx

2442 ms

GetImg.aspx

GetImg.aspx

2497 ms

GetImg.aspx

GetImg.aspx

2341 ms

GetImg.aspx

GetImg.aspx

2385 ms

GetImg.aspx

GetImg.aspx

2417 ms

GetImg.aspx

GetImg.aspx

2260 ms

GetImg.aspx

GetImg.aspx

2340 ms

crown.png

crown.png

2254 ms

line_ranking.png

line_ranking.png

2168 ms

GetImg.aspx

GetImg.aspx

2245 ms

GetImg.aspx

GetImg.aspx

3262 ms

GetImg.aspx

GetImg.aspx

2288 ms

GetImg.aspx

GetImg.aspx

2759 ms

GetImg.aspx

GetImg.aspx

2651 ms

GetImg.aspx

GetImg.aspx

2214 ms

GetImg.aspx

GetImg.aspx

2291 ms

GetImg.aspx

GetImg.aspx

2365 ms

GetImg.aspx

GetImg.aspx

2335 ms

GetImg.aspx

GetImg.aspx

2435 ms

GetImg.aspx

GetImg.aspx

2451 ms

GetImg.aspx

GetImg.aspx

2527 ms

GetImg.aspx

GetImg.aspx

2557 ms

GetImg.aspx

GetImg.aspx

2386 ms

GetImg.aspx

GetImg.aspx

2199 ms

GetImg.aspx

GetImg.aspx

2183 ms

GetImg.aspx

GetImg.aspx

2299 ms

GetImg.aspx

GetImg.aspx

2282 ms

GetImg.aspx

GetImg.aspx

2499 ms

GetImg.aspx

GetImg.aspx

1946 ms

GetImg.aspx

GetImg.aspx

1915 ms

GetImg.aspx

GetImg.aspx

1927 ms

bg_life.png

bg_life.png

1852 ms

line.svg

line.svg

1889 ms

bg_footer_slider.png

bg_footer_slider.png

1836 ms

bg_footer.png

bg_footer.png

1812 ms

transparent.png

transparent.png

1900 ms

bx_loader.gif

bx_loader.gif

1834 ms

slider-arrow.png

slider-arrow.png

1866 ms

Accessibility Review

foodnext.net accessibility score

65

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

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

    N/A

  • 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 neither this language nor any other was claimed in <html> or <meta> tags. 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

foodnext.net

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: