Tools & Wizards About Us
thefutureishere.economist.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

thefutureishere.economist.com

REDEFINING LIMITS: The Future of Sports and Technology - Toray

Page Load Speed

5.3 sec in total

First Response

398 ms

Resources Loaded

4.6 sec

Page Rendered

261 ms

thefutureishere.economist.com screenshot

About Website

Click here to check amazing The Future Ishere Economist content for United States. Otherwise, check out these important facts you probably never knew about thefutureishere.economist.com

Technology has helped propel a better understanding of the science of training and the readiness of athletes, which have both continued to redefine the limits of athletes and para athletes. How far ha...

Visit thefutureishere.economist.com

Key Findings

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

Performance Metrics

thefutureishere.economist.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value25.6 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value1.085

2/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

thefutureishere.economist.com

398 ms

css

18 ms

zlq3bxh.css

262 ms

jquery.mCustomScrollbar.min.css

149 ms

style.min.css

518 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 74% of them (60 requests) were addressed to the original Thefutureishere.economist.com, 5% (4 requests) were made to Use.typekit.net and 4% (3 requests) were made to Metrics.brightcove.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Players.brightcove.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 844.0 kB (22%)

Content Size

3.8 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thefutureishere.economist.com main page is 3.8 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.7 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 193.5 kB

  • Original 239.4 kB
  • After minification 194.3 kB
  • After compression 45.9 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 45.1 kB, which is 19% 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 193.5 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 26.5 kB

  • Original 2.7 MB
  • After minification 2.7 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. The Future Ishere Economist images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 261.1 kB

  • Original 406.8 kB
  • After minification 369.3 kB
  • After compression 145.6 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 261.1 kB or 64% of the original size.

CSS Optimization

-89%

Potential reduce by 362.8 kB

  • Original 405.9 kB
  • After minification 329.9 kB
  • After compression 43.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. Thefutureishere.economist.com needs all CSS files to be minified and compressed as it can save up to 362.8 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (43%)

Requests Now

67

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thefutureishere.economist.com

thefutureishere.economist.com

398 ms

css

css

18 ms

zlq3bxh.css

zlq3bxh.css

262 ms

jquery.mCustomScrollbar.min.css

jquery.mCustomScrollbar.min.css

149 ms

style.min.css

style.min.css

518 ms

video-js.min.css

video-js.min.css

147 ms

cmp.min.js

cmp.min.js

13 ms

embed.js

embed.js

369 ms

index.min.js

index.min.js

1179 ms

jquery.min.js

jquery.min.js

96 ms

blazy.min.js

blazy.min.js

95 ms

scrolloverflow.min.js

scrolloverflow.min.js

95 ms

fullpage.min.js

fullpage.min.js

186 ms

lethargy.min.js

lethargy.min.js

158 ms

TweenMax.min.js

TweenMax.min.js

187 ms

config.js

config.js

158 ms

ecosocial.js

ecosocial.js

157 ms

running-section.js

running-section.js

195 ms

video.js

video.js

199 ms

layer.js

layer.js

231 ms

tracking.js

tracking.js

230 ms

script.js

script.js

231 ms

p.css

p.css

191 ms

close-icon.png

close-icon.png

568 ms

toray-logo.svg

toray-logo.svg

544 ms

running.jpg

running.jpg

590 ms

tennis.jpg

tennis.jpg

664 ms

number.jpg

number.jpg

579 ms

gym.jpg

gym.jpg

618 ms

runningman.jpg

runningman.jpg

616 ms

swimming.jpg

swimming.jpg

572 ms

eiu.svg

eiu.svg

574 ms

down-arrow-2.svg

down-arrow-2.svg

576 ms

article1image1.png

article1image1.png

578 ms

article1image2.png

article1image2.png

601 ms

article1image3.png

article1image3.png

654 ms

i-expander-x.svg

i-expander-x.svg

636 ms

close-blue.svg

close-blue.svg

648 ms

blog1image1.png

blog1image1.png

650 ms

blog1image3.png

blog1image3.png

647 ms

blog2image1.png

blog2image1.png

646 ms

blog2image2.png

blog2image2.png

703 ms

blog3image2.png

blog3image2.png

691 ms

blog4image1.png

blog4image1.png

702 ms

blog4image2.png

blog4image2.png

691 ms

article2image1.png

article2image1.png

691 ms

article2image2.png

article2image2.png

691 ms

article2image3.png

article2image3.png

694 ms

placeholder1.jpg

placeholder1.jpg

693 ms

placeholder2.jpg

placeholder2.jpg

692 ms

placeholder3.jpg

placeholder3.jpg

737 ms

toray-sample.jpg

toray-sample.jpg

731 ms

arrow-up-blue.svg

arrow-up-blue.svg

733 ms

arrow-down-blue.svg

arrow-down-blue.svg

729 ms

icon-linkedin.svg

icon-linkedin.svg

804 ms

icon-twitter.svg

icon-twitter.svg

770 ms

icon-fb.svg

icon-fb.svg

853 ms

icon-mail.svg

icon-mail.svg

880 ms

HelveticaNeue.woff

HelveticaNeue.woff

1092 ms

HelveticaNeueMedium.woff

HelveticaNeueMedium.woff

1039 ms

HelveticaNeueBold.woff

HelveticaNeueBold.woff

1034 ms

d

d

1031 ms

d

d

1064 ms

d

d

1062 ms

EconSansOS-Light.woff

EconSansOS-Light.woff

1089 ms

EconSansOS-Regular.woff

EconSansOS-Regular.woff

1061 ms

EconSansOS-Medium.woff

EconSansOS-Medium.woff

1060 ms

EconSansOS-Bold.woff

EconSansOS-Bold.woff

1059 ms

EconSansOS-ExtraBold.woff

EconSansOS-ExtraBold.woff

1058 ms

tracker

tracker

270 ms

6112451270001

6112451270001

393 ms

tracker

tracker

256 ms

I5YL3XhodRRsVWZe4NnZOhWnSAWgxhMoEr6SmzZieF43Mk7ZOBdeCVGrp9Eu+54J2xhySplfB5XHwQLXUmT9KH6+kPnQ7ZYuIEzNyfs1DLU1VU4SWZ6LkXGHsD1ZKbMw=

I5YL3XhodRRsVWZe4NnZOhWnSAWgxhMoEr6SmzZieF43Mk7ZOBdeCVGrp9Eu+54J2xhySplfB5XHwQLXUmT9KH6+kPnQ7ZYuIEzNyfs1DLU1VU4SWZ6LkXGHsD1ZKbMw=

151 ms

tracker

tracker

93 ms

analytics.js

analytics.js

101 ms

insight.min.js

insight.min.js

254 ms

bosh.svg

bosh.svg

187 ms

bk-coretag.js

bk-coretag.js

207 ms

collect

collect

217 ms

19805

19805

139 ms

24 ms

Accessibility Review

thefutureishere.economist.com accessibility score

78

Accessibility Issues

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

thefutureishere.economist.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

thefutureishere.economist.com SEO score

83

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thefutureishere.economist.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Thefutureishere.economist.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

thefutureishere.economist.com

Open Graph data is detected on the main page of The Future Ishere Economist. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: