Tools & Wizards About Us
forwardjs.com screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

forwardjs.com

ForwardJS - Ottawa Meetup

Page Load Speed

1.4 sec in total

First Response

193 ms

Resources Loaded

1.1 sec

Page Rendered

172 ms

forwardjs.com screenshot

About Website

Click here to check amazing ForwardJS content for United States. Otherwise, check out these important facts you probably never knew about forwardjs.com

Join ForwardJS Ottawa Meetup - Connect with fellow JavaScript developers and learn from industry experts

Visit forwardjs.com

Key Findings

We analyzed Forwardjs.com page load time and found that the first response time was 193 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

forwardjs.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value3.7 s

86/100

10%

TBT (Total Blocking Time)

Value1,300 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.2 s

85/100

10%

Network Requests Diagram

forwardjs.com

193 ms

forwardjs.com

346 ms

E-v1.js

21 ms

webpack-runtime-4b3c6607aab1e071dc86.js

190 ms

app-d857590435df4f80d3ec.js

449 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 77% of them (10 requests) were addressed to the original Forwardjs.com, 23% (3 requests) were made to Fast.wistia.com. The less responsive or slowest element that took the longest time to load (517 ms) belongs to the original domain Forwardjs.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 158.7 kB (32%)

Content Size

489.5 kB

After Optimization

330.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Forwardjs.com main page is 489.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. HTML takes 192.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 158.7 kB

  • Original 192.8 kB
  • After minification 192.8 kB
  • After compression 34.1 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 158.7 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 150.1 kB
  • After minification 150.1 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. ForwardJS images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 146.6 kB
  • After minification 146.6 kB
  • After compression 146.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. This website has mostly compressed JavaScripts.

Requests Breakdown

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

Requests Now

11

After Optimization

5

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

forwardjs.com

forwardjs.com

193 ms

forwardjs.com

forwardjs.com

346 ms

E-v1.js

E-v1.js

21 ms

webpack-runtime-4b3c6607aab1e071dc86.js

webpack-runtime-4b3c6607aab1e071dc86.js

190 ms

app-d857590435df4f80d3ec.js

app-d857590435df4f80d3ec.js

449 ms

commons-bc55a768d1a54b9845c3.js

commons-bc55a768d1a54b9845c3.js

491 ms

component---src-pages-index-js-74d77ae0bc4360f0aac1.js

component---src-pages-index-js-74d77ae0bc4360f0aac1.js

312 ms

styles-2dc83d82bedd1a58a7c1.js

styles-2dc83d82bedd1a58a7c1.js

196 ms

nav-arrow-c455ecee56d81fcffa5bd056b1bb2ab1.svg

nav-arrow-c455ecee56d81fcffa5bd056b1bb2ab1.svg

306 ms

nav-logo-01c96b10da9debf2c48e9ca4fc2a3e78.svg

nav-logo-01c96b10da9debf2c48e9ca4fc2a3e78.svg

372 ms

bg-image-masks-6fdd82f45b87519cc1c292fbb5066f14.jpg

bg-image-masks-6fdd82f45b87519cc1c292fbb5066f14.jpg

517 ms

ba84q1a3n8.json

ba84q1a3n8.json

26 ms

ba84q1a3n8

ba84q1a3n8

3 ms

Accessibility Review

forwardjs.com accessibility score

95

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.

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

Links do not have a discernible name

Best Practices

forwardjs.com best practices score

92

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

Page has valid source maps

SEO Factors

forwardjs.com SEO score

90

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forwardjs.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 Forwardjs.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

forwardjs.com

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