Tools & Wizards About Us

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

future.ca

Electronic Components Distributor | Future Electronics

Page Load Speed

1.1 sec in total

First Response

119 ms

Resources Loaded

904 ms

Page Rendered

114 ms

About Website

Visit future.ca now to see the best up-to-date Future content for Canada and also check out these interesting facts you probably never knew about future.ca

Global electronic components distributor with huge inventory of in stock and same day ready to ship electronic components.

Visit future.ca

Key Findings

We analyzed Future.ca page load time and found that the first response time was 119 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

future.ca performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value34.1 s

0/100

25%

SI (Speed Index)

Value64.1 s

0/100

10%

TBT (Total Blocking Time)

Value75,760 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.34

33/100

15%

TTI (Time to Interactive)

Value101.0 s

0/100

10%

Network Requests Diagram

future.ca

119 ms

WebsiteLanding.aspx

74 ms

fe-2.0.css

52 ms

en-us-2.0.css

23 ms

seoNavJquery.js

89 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 8% of them (1 request) were addressed to the original Future.ca, 77% (10 requests) were made to Futureelectronics.com and 15% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (119 ms) belongs to the original domain Future.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 217.9 kB (73%)

Content Size

297.5 kB

After Optimization

79.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Future.ca main page is 297.5 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. CSS take 197.1 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 5.9 kB

  • Original 9.5 kB
  • After minification 9.3 kB
  • After compression 3.6 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 5.9 kB or 62% of the original size.

Image Optimization

-20%

Potential reduce by 3.0 kB

  • Original 15.2 kB
  • After minification 12.2 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. Obviously, Future needs image optimization as it can save up to 3.0 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-51%

Potential reduce by 38.5 kB

  • Original 75.8 kB
  • After minification 75.7 kB
  • After compression 37.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 38.5 kB or 51% of the original size.

CSS Optimization

-86%

Potential reduce by 170.4 kB

  • Original 197.1 kB
  • After minification 145.0 kB
  • After compression 26.7 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. Future.ca needs all CSS files to be minified and compressed as it can save up to 170.4 kB or 86% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

11

After Optimization

11

  • Images
  • JavaScript
  • CSS

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Future. According to our analytics all requests are already optimized.

Network Requests Diagram

Accessibility Review

future.ca accessibility score

72

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

future.ca 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

Missing source maps for large first-party JavaScript

SEO Factors

future.ca SEO score

77

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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