Tools & Wizards About Us
go.amazing.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

go.amazing.com

Amazing - The #1 Training Platform for Building a Business Online

Page Load Speed

2.3 sec in total

First Response

30 ms

Resources Loaded

1.1 sec

Page Rendered

1.2 sec

go.amazing.com screenshot

About Website

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

Visit go.amazing.com

Key Findings

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

Performance Metrics

go.amazing.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value4,150 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

go.amazing.com

30 ms

amazing.com

199 ms

slick.css

55 ms

all.css

110 ms

main.min.css

40 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Go.amazing.com, 67% (47 requests) were made to Amazing.com and 7% (5 requests) were made to Site-assets.fontawesome.com. The less responsive or slowest element that took the longest time to load (709 ms) relates to the external source Amazing.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 796.5 kB (31%)

Content Size

2.6 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Go.amazing.com main page is 2.6 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. 75% 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 342.8 kB

  • Original 370.7 kB
  • After minification 299.4 kB
  • After compression 27.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 71.3 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 342.8 kB or 92% of the original size.

Image Optimization

-0%

Potential reduce by 6.7 kB

  • Original 1.4 MB
  • After minification 1.3 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. Go Amazing images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 440.1 kB

  • Original 723.9 kB
  • After minification 723.9 kB
  • After compression 283.7 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 440.1 kB or 61% of the original size.

CSS Optimization

-6%

Potential reduce by 6.9 kB

  • Original 119.7 kB
  • After minification 119.7 kB
  • After compression 112.8 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. Go.amazing.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (45%)

Requests Now

62

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

go.amazing.com

go.amazing.com

30 ms

amazing.com

amazing.com

199 ms

slick.css

slick.css

55 ms

all.css

all.css

110 ms

main.min.css

main.min.css

40 ms

theme-overrides.css

theme-overrides.css

59 ms

module_112561637455_Buttons_3.min.css

module_112561637455_Buttons_3.min.css

45 ms

module_98218622271_featured_partner_logo_module.min.css

module_98218622271_featured_partner_logo_module.min.css

72 ms

module_98669415279_footer_module.min.css

module_98669415279_footer_module.min.css

70 ms

js

js

93 ms

proof.js

proof.js

69 ms

jquery-1.7.1.js

jquery-1.7.1.js

69 ms

embed.js

embed.js

61 ms

slick.min.js

slick.min.js

66 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

80 ms

jquery.countup.js

jquery.countup.js

69 ms

main.min.js

main.min.js

91 ms

project.js

project.js

101 ms

module_98209483818_header_module.min.js

module_98209483818_header_module.min.js

98 ms

project.js

project.js

95 ms

loader.js

loader.js

70 ms

v2.js

v2.js

285 ms

22696337.js

22696337.js

288 ms

index.js

index.js

283 ms

gtm.js

gtm.js

150 ms

arrow.png

arrow.png

378 ms

header_logo.png

header_logo.png

354 ms

academy-hero-bg2.jpg

academy-hero-bg2.jpg

354 ms

business_Insider.png

business_Insider.png

389 ms

msn.png

msn.png

393 ms

cnbc.png

cnbc.png

354 ms

entrepreneur.png

entrepreneur.png

446 ms

success.png

success.png

356 ms

forbes.png

forbes.png

357 ms

expertImg.jpg

expertImg.jpg

355 ms

play-btn.png

play-btn.png

359 ms

expertImg2.jpg

expertImg2.jpg

359 ms

expertImg3.jpg

expertImg3.jpg

360 ms

expertImg5.jpg

expertImg5.jpg

361 ms

bookbgimage.png

bookbgimage.png

361 ms

book.png

book.png

361 ms

Sara%20N.jpeg

Sara%20N.jpeg

362 ms

Niki%20B.jpeg

Niki%20B.jpeg

391 ms

Joycelyn%20W.%20.jpeg

Joycelyn%20W.%20.jpeg

386 ms

Paul%20N.jpg

Paul%20N.jpg

418 ms

Jada%20M.jpeg

Jada%20M.jpeg

406 ms

Dushmantha%20.jpeg

Dushmantha%20.jpeg

635 ms

Heather%20H.jpeg

Heather%20H.jpeg

445 ms

Abduallah%20I%20.jpeg

Abduallah%20I%20.jpeg

499 ms

Sabrina%20J%20.png

Sabrina%20J%20.png

709 ms

entrepreneursImg.png

entrepreneursImg.png

535 ms

Untitled-1.png

Untitled-1.png

538 ms

Untitled-3.png

Untitled-3.png

538 ms

SaraBlakely.png

SaraBlakely.png

574 ms

Layer-61_a.png

Layer-61_a.png

576 ms

quote.png

quote.png

355 ms

index.html

index.html

291 ms

firebase.js

firebase.js

93 ms

proxy.js

proxy.js

34 ms

regular.woff

regular.woff

217 ms

700.woff

700.woff

252 ms

fa-regular-400.ttf

fa-regular-400.ttf

142 ms

fa-light-300.ttf

fa-light-300.ttf

174 ms

fa-thin-100.ttf

fa-thin-100.ttf

175 ms

fa-solid-900.ttf

fa-solid-900.ttf

176 ms

22696337.js

22696337.js

232 ms

web-interactives-embed.js

web-interactives-embed.js

132 ms

collectedforms.js

collectedforms.js

153 ms

banner.js

banner.js

232 ms

fb.js

fb.js

153 ms

Accessibility Review

go.amazing.com accessibility score

83

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible 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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

go.amazing.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

go.amazing.com SEO score

81

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

go.amazing.com

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