Tools & Wizards About Us
flax.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

flax.com

Page Load Speed

3.7 sec in total

First Response

324 ms

Resources Loaded

3.2 sec

Page Rendered

105 ms

flax.com screenshot

About Website

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

Find Flax Information about; flax seed, flax seed oil and fish oil, including nutrition, health benefits, and flax seed. Links to lots of yummy recipes that include flax.

Visit flax.com

Key Findings

We analyzed Flax.com page load time and found that the first response time was 324 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

flax.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value3,270 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

flax.com

324 ms

swfobject.2.1.js

105 ms

highslide-with-html.4.1.9.js

120 ms

calendar_popup.js

111 ms

sprintf.js

107 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 97% of them (37 requests) were addressed to the original Flax.com, 3% (1 request) were made to Adobe.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Flax.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 179.4 kB (51%)

Content Size

349.0 kB

After Optimization

169.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flax.com main page is 349.0 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. 20% of websites need less resources to load. Javascripts take 132.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 80.2 kB

  • Original 97.3 kB
  • After minification 96.3 kB
  • After compression 17.2 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 80.2 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 310 B

  • Original 119.3 kB
  • After minification 119.0 kB

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. Flax images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 98.9 kB

  • Original 132.3 kB
  • After minification 114.9 kB
  • After compression 33.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 98.9 kB or 75% of the original size.

CSS Optimization

-21%

Potential reduce by 7 B

  • Original 33 B
  • After minification 26 B
  • After compression 26 B

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. Flax.com needs all CSS files to be minified and compressed as it can save up to 7 B or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (46%)

Requests Now

37

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flax.com

flax.com

324 ms

swfobject.2.1.js

swfobject.2.1.js

105 ms

highslide-with-html.4.1.9.js

highslide-with-html.4.1.9.js

120 ms

calendar_popup.js

calendar_popup.js

111 ms

sprintf.js

sprintf.js

107 ms

tabbed_items_default.js

tabbed_items_default.js

115 ms

tabbed_items_default_css_generated.js

tabbed_items_default_css_generated.js

139 ms

get_flash_player.gif

get_flash_player.gif

9 ms

background.jpg

background.jpg

93 ms

wheel.gif

wheel.gif

128 ms

dialog_close.gif

dialog_close.gif

96 ms

error_bg.jpg

error_bg.jpg

94 ms

error_header.gif

error_header.gif

103 ms

warning_bg.jpg

warning_bg.jpg

101 ms

warning_header.gif

warning_header.gif

188 ms

success_bg.jpg

success_bg.jpg

200 ms

success_header.gif

success_header.gif

192 ms

prompt_bg.jpg

prompt_bg.jpg

750 ms

prompt_header.gif

prompt_header.gif

881 ms

body_back.jpg

body_back.jpg

1138 ms

header.jpg

header.jpg

1161 ms

link_arrow.gif

link_arrow.gif

1250 ms

rounded_top.jpg

rounded_top.jpg

256 ms

recipe1.jpg

recipe1.jpg

1907 ms

recipe2.jpg

recipe2.jpg

2022 ms

recipe3.jpg

recipe3.jpg

2033 ms

recipe4.jpg

recipe4.jpg

2153 ms

rounded_bottom.jpg

rounded_bottom.jpg

2141 ms

small_rounded_top.jpg

small_rounded_top.jpg

2143 ms

small_rounded_bottom.jpg

small_rounded_bottom.jpg

2153 ms

video_thumb.jpg

video_thumb.jpg

2156 ms

homepage_family.jpg

homepage_family.jpg

2148 ms

tabbed_items_default.css

tabbed_items_default.css

2232 ms

flax.com

flax.com

287 ms

footer_back.jpg

footer_back.jpg

104 ms

rounded-white.png

rounded-white.png

244 ms

loader.white.gif

loader.white.gif

95 ms

zoomout.cur

zoomout.cur

267 ms

Accessibility Review

flax.com accessibility score

64

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-*] attributes do not have valid values

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

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.

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

flax.com 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

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

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

Page is blocked from indexing

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

    N/A

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flax.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Flax.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

flax.com

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