Tools & Wizards About Us
soup11.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

soup11.com

Soup | Jon Gordon

Page Load Speed

2.3 sec in total

First Response

124 ms

Resources Loaded

1.5 sec

Page Rendered

718 ms

soup11.com screenshot

About Website

Click here to check amazing Soup 11 content. Otherwise, check out these important facts you probably never knew about soup11.com

Soup, an inspirational business fable, shares a recipe for success filled with the essential ingredients to build a winning team and create a culture of greatness. Only a few months into her new job, ...

Visit soup11.com

Key Findings

We analyzed Soup11.com page load time and found that the first response time was 124 ms and then it took 2.2 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

soup11.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value1,580 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.072

96/100

15%

TTI (Time to Interactive)

Value17.9 s

4/100

10%

Network Requests Diagram

soup11.com

124 ms

115 ms

81 ms

siteground-optimizer-combined-css-e641dc0c21267da2813da0243ef3d089.css

114 ms

utq7jtg.css

86 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Soup11.com, 49% (32 requests) were made to Jongordon.com and 18% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (486 ms) relates to the external source Jongordon.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 264.8 kB (18%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Soup11.com main page is 1.5 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. 60% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 92.3 kB

  • Original 112.4 kB
  • After minification 111.5 kB
  • After compression 20.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 92.3 kB or 82% of the original size.

Image Optimization

-11%

Potential reduce by 108.4 kB

  • Original 1.0 MB
  • After minification 912.9 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, Soup 11 needs image optimization as it can save up to 108.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-15%

Potential reduce by 32.5 kB

  • Original 211.8 kB
  • After minification 211.8 kB
  • After compression 179.3 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 32.5 kB or 15% of the original size.

CSS Optimization

-21%

Potential reduce by 31.7 kB

  • Original 147.9 kB
  • After minification 147.9 kB
  • After compression 116.3 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. Soup11.com needs all CSS files to be minified and compressed as it can save up to 31.7 kB or 21% of the original size.

Requests Breakdown

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

Requests Now

39

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

soup11.com

soup11.com

124 ms

115 ms

81 ms

siteground-optimizer-combined-css-e641dc0c21267da2813da0243ef3d089.css

siteground-optimizer-combined-css-e641dc0c21267da2813da0243ef3d089.css

114 ms

utq7jtg.css

utq7jtg.css

86 ms

sbi-styles.min.css

sbi-styles.min.css

111 ms

magnific-popup.min.css

magnific-popup.min.css

35 ms

jquery.min.js

jquery.min.js

153 ms

v2.js

v2.js

59 ms

6354845.js

6354845.js

72 ms

js

js

77 ms

slick.min.css

slick.min.css

43 ms

slick-theme.min.css

slick-theme.min.css

49 ms

hooks.min.js

hooks.min.js

137 ms

i18n.min.js

i18n.min.js

136 ms

siteground-optimizer-combined-js-8a3b6594f802a16b76f84602bf23853e.js

siteground-optimizer-combined-js-8a3b6594f802a16b76f84602bf23853e.js

235 ms

p.css

p.css

81 ms

fbevents.js

fbevents.js

70 ms

gtm.js

gtm.js

56 ms

sbi-sprite.png

sbi-sprite.png

182 ms

site-logo.svg

site-logo.svg

182 ms

book-single-bg-scaled.webp

book-single-bg-scaled.webp

183 ms

soup-687x1024.jpg.webp

soup-687x1024.jpg.webp

181 ms

bx_link.svg

bx_link.svg

181 ms

home-sec4-bg.jpg

home-sec4-bg.jpg

293 ms

DifficultConversationsBestseller.png.webp

DifficultConversationsBestseller.png.webp

265 ms

SuccessJournal.jpg.webp

SuccessJournal.jpg.webp

256 ms

EnergyBusCover-Int400.jpeg.webp

EnergyBusCover-Int400.jpeg.webp

256 ms

Energy-Bus-for-Schools-Cover-Hi-Res-scaled.jpg.webp

Energy-Bus-for-Schools-Cover-Hi-Res-scaled.jpg.webp

324 ms

POPL-CoverFlat.png.webp

POPL-CoverFlat.png.webp

452 ms

OneTruthWSJ.png.webp

OneTruthWSJ.png.webp

486 ms

ppt.png.webp

ppt.png.webp

413 ms

training-camp.jpg.webp

training-camp.jpg.webp

416 ms

carpenter.jpg.webp

carpenter.jpg.webp

413 ms

coffee-bean.jpg.webp

coffee-bean.jpg.webp

415 ms

WSJ-How-to-be-a-Coffee-Bean.jpg.webp

WSJ-How-to-be-a-Coffee-Bean.jpg.webp

450 ms

footer-img4-_1_-841x1024.webp

footer-img4-_1_-841x1024.webp

450 ms

footer2-bg-scaled.webp

footer2-bg-scaled.webp

451 ms

footer-logo.svg

footer-logo.svg

452 ms

web-interactives-embed.js

web-interactives-embed.js

211 ms

6354845.js

6354845.js

306 ms

fb.js

fb.js

203 ms

banner.js

banner.js

252 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

39 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

66 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

80 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

93 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

92 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

90 ms

d

d

10 ms

d

d

28 ms

d

d

28 ms

d

d

29 ms

d

d

36 ms

d

d

36 ms

fa-brands-400.woff

fa-brands-400.woff

314 ms

fa-solid-900.woff

fa-solid-900.woff

349 ms

fa-regular-400.woff

fa-regular-400.woff

320 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

90 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

123 ms

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

89 ms

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

109 ms

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

91 ms

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

123 ms

AcuminProExtraCond-Regular.woff

AcuminProExtraCond-Regular.woff

320 ms

Accessibility Review

soup11.com accessibility score

69

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

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.

Best Practices

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

Page has valid source maps

SEO Factors

soup11.com SEO score

76

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

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

soup11.com

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