Tools & Wizards About Us
36south.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

36south.com

36 South Capital Advisors, London | We are a leading volatility and tail risk manager based in London

Page Load Speed

5.2 sec in total

First Response

499 ms

Resources Loaded

4.5 sec

Page Rendered

239 ms

36south.com screenshot

About Website

Welcome to 36south.com homepage info - get ready to check 36 South best content right away, or after learning these important things about 36south.com

36 South, Capital Advisors, London | We are a leading volatility and tail risk manager based in London

Visit 36south.com

Key Findings

We analyzed 36south.com page load time and found that the first response time was 499 ms and then it took 4.7 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

36south.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

36south.com

499 ms

www.36south.com

1076 ms

slippry.css

226 ms

styles.css

666 ms

extra.css

890 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 97% of them (36 requests) were addressed to the original 36south.com, 3% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain 36south.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 199.8 kB (11%)

Content Size

1.8 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-70%

Potential reduce by 6.6 kB

  • Original 9.4 kB
  • After minification 8.8 kB
  • After compression 2.8 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 6.6 kB or 70% of the original size.

Image Optimization

-2%

Potential reduce by 35.4 kB

  • Original 1.6 MB
  • After minification 1.6 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. 36 South images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 113.2 kB

  • Original 173.4 kB
  • After minification 169.4 kB
  • After compression 60.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 113.2 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 44.5 kB

  • Original 52.8 kB
  • After minification 44.6 kB
  • After compression 8.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. 36south.com needs all CSS files to be minified and compressed as it can save up to 44.5 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

18

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

36south.com

36south.com

499 ms

www.36south.com

www.36south.com

1076 ms

slippry.css

slippry.css

226 ms

styles.css

styles.css

666 ms

extra.css

extra.css

890 ms

css.html

css.html

880 ms

jquery.js

jquery.js

1337 ms

modernizr.js

modernizr.js

1104 ms

common.js

common.js

895 ms

js.html

js.html

884 ms

slippry.js

slippry.js

1100 ms

scripts.js

scripts.js

1103 ms

analytics.js

analytics.js

1328 ms

ldn-header.jpg

ldn-header.jpg

1343 ms

36south-logo.png

36south-logo.png

441 ms

down-arrow.png

down-arrow.png

252 ms

05.jpg

05.jpg

895 ms

04.jpg

04.jpg

881 ms

01.jpg

01.jpg

1118 ms

FiraSans-Medium.woff

FiraSans-Medium.woff

453 ms

FiraSans-Regular.woff

FiraSans-Regular.woff

641 ms

FiraSans-Light.woff

FiraSans-Light.woff

669 ms

FiraSans-ExtraLight.woff

FiraSans-ExtraLight.woff

858 ms

FiraSans-SemiBold.woff

FiraSans-SemiBold.woff

886 ms

FiraSans-Bold.woff

FiraSans-Bold.woff

1074 ms

FiraSans-ExtraBold.woff

FiraSans-ExtraBold.woff

1081 ms

sy-loader.gif

sy-loader.gif

1084 ms

prev-arrow.png

prev-arrow.png

1096 ms

next-arrow.png

next-arrow.png

1281 ms

collect

collect

20 ms

FiraSans-Medium.ttf

FiraSans-Medium.ttf

842 ms

FiraSans-Regular.ttf

FiraSans-Regular.ttf

667 ms

FiraSans-Light.ttf

FiraSans-Light.ttf

646 ms

FiraSans-ExtraLight.ttf

FiraSans-ExtraLight.ttf

463 ms

FiraSans-SemiBold.ttf

FiraSans-SemiBold.ttf

620 ms

FiraSans-Bold.ttf

FiraSans-Bold.ttf

437 ms

FiraSans-ExtraBold.ttf

FiraSans-ExtraBold.ttf

444 ms

Accessibility Review

36south.com accessibility score

77

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

36south.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

SEO Factors

36south.com SEO score

89

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

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 36south.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 36south.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

36south.com

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