Tools & Wizards About Us
slate.co screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

slate.co

Modern super built by humans, powered by technology | Slate Super

Page Load Speed

9.2 sec in total

First Response

1.6 sec

Resources Loaded

6.8 sec

Page Rendered

839 ms

slate.co screenshot

About Website

Welcome to slate.co homepage info - get ready to check Slate best content right away, or after learning these important things about slate.co

Join Slate Super. Now there's a better way to take control of your financial future⁠—with an ethical super experience that just works.

Visit slate.co

Key Findings

We analyzed Slate.co page load time and found that the first response time was 1.6 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

slate.co performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value21.8 s

0/100

10%

TBT (Total Blocking Time)

Value15,730 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value34.5 s

0/100

10%

Network Requests Diagram

slate.co

1613 ms

autoptimize_b241c278ec22d4c908b6682beb407cff.css

155 ms

autoptimize_single_7b8daf750636d0d5647813269286bde6.css

93 ms

autoptimize_single_32f4a6064610488ffabdd03e1896d91c.css

93 ms

jquery.min.js

91 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 57% of them (33 requests) were addressed to the original Slate.co, 19% (11 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Slate.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 513.3 kB (49%)

Content Size

1.1 MB

After Optimization

536.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Slate.co main page is 1.1 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. 70% of websites need less resources to load. Images take 603.1 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 68.8 kB

  • Original 84.4 kB
  • After minification 84.4 kB
  • After compression 15.6 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 68.8 kB or 82% of the original size.

Image Optimization

-23%

Potential reduce by 138.2 kB

  • Original 603.1 kB
  • After minification 464.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, Slate needs image optimization as it can save up to 138.2 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 109 B

  • Original 53.9 kB
  • After minification 53.9 kB
  • After compression 53.8 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.

CSS Optimization

-99%

Potential reduce by 306.2 kB

  • Original 308.7 kB
  • After minification 2.5 kB
  • After compression 2.5 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. Slate.co needs all CSS files to be minified and compressed as it can save up to 306.2 kB or 99% of the original size.

Requests Breakdown

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

Requests Now

38

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

slate.co

slate.co

1613 ms

autoptimize_b241c278ec22d4c908b6682beb407cff.css

autoptimize_b241c278ec22d4c908b6682beb407cff.css

155 ms

autoptimize_single_7b8daf750636d0d5647813269286bde6.css

autoptimize_single_7b8daf750636d0d5647813269286bde6.css

93 ms

autoptimize_single_32f4a6064610488ffabdd03e1896d91c.css

autoptimize_single_32f4a6064610488ffabdd03e1896d91c.css

93 ms

jquery.min.js

jquery.min.js

91 ms

slate.co

slate.co

1086 ms

snippet.js

snippet.js

639 ms

css

css

639 ms

fbevents.js

fbevents.js

76 ms

wp-polyfill.min.js

wp-polyfill.min.js

58 ms

i18n.min.js

i18n.min.js

33 ms

e-202240.js

e-202240.js

128 ms

autoptimize_4bc12c108b97721ca0a13ce3a963c234.js

autoptimize_4bc12c108b97721ca0a13ce3a963c234.js

130 ms

identity.js

identity.js

8 ms

556179035069424

556179035069424

95 ms

ga.js

ga.js

253 ms

slate-logo-1.png

slate-logo-1.png

1497 ms

slate-logo-1.png

slate-logo-1.png

306 ms

Slate-app-gif-332x684white-1.gif

Slate-app-gif-332x684white-1.gif

366 ms

icon-life.svg

icon-life.svg

299 ms

icon-phone-grn.svg

icon-phone-grn.svg

210 ms

icon-support.svg

icon-support.svg

1350 ms

Slate-app-On-Track-332x684grey.gif

Slate-app-On-Track-332x684grey.gif

4558 ms

Garden@2x-768x496.png

Garden@2x-768x496.png

362 ms

Retire.png

Retire.png

361 ms

Window.png

Window.png

363 ms

Walking-1@2x-oykpgabkkqrghaqxw1nomw73gx3i7du481xr0r4am0.png

Walking-1@2x-oykpgabkkqrghaqxw1nomw73gx3i7du481xr0r4am0.png

500 ms

icon-document.png

icon-document.png

493 ms

icon-brochure.png

icon-brochure.png

492 ms

icon-checklist.png

icon-checklist.png

1464 ms

slate-logo-light-1.png

slate-logo-light-1.png

1019 ms

slate-logo-light-1.png

slate-logo-light-1.png

2469 ms

o-0IIpQlx3QUlC5A4PNr5TRF.ttf

o-0IIpQlx3QUlC5A4PNr5TRF.ttf

315 ms

o-0NIpQlx3QUlC5A4PNjFhdVZNyE.ttf

o-0NIpQlx3QUlC5A4PNjFhdVZNyE.ttf

315 ms

o-0NIpQlx3QUlC5A4PNjThZVZNyE.ttf

o-0NIpQlx3QUlC5A4PNjThZVZNyE.ttf

845 ms

o-0NIpQlx3QUlC5A4PNjKhVVZNyE.ttf

o-0NIpQlx3QUlC5A4PNjKhVVZNyE.ttf

845 ms

o-0OIpQlx3QUlC5A4PNjhgRCQ_w.ttf

o-0OIpQlx3QUlC5A4PNjhgRCQ_w.ttf

1018 ms

o-0NIpQlx3QUlC5A4PNjOhBVZNyE.ttf

o-0NIpQlx3QUlC5A4PNjOhBVZNyE.ttf

1019 ms

o-0NIpQlx3QUlC5A4PNjXhFVZNyE.ttf

o-0NIpQlx3QUlC5A4PNjXhFVZNyE.ttf

1016 ms

o-0NIpQlx3QUlC5A4PNjQhJVZNyE.ttf

o-0NIpQlx3QUlC5A4PNjQhJVZNyE.ttf

1017 ms

o-0NIpQlx3QUlC5A4PNjZhNVZNyE.ttf

o-0NIpQlx3QUlC5A4PNjZhNVZNyE.ttf

1017 ms

ga6Iaw1J5X9T9RW6j9bNfFcWbQ.ttf

ga6Iaw1J5X9T9RW6j9bNfFcWbQ.ttf

1018 ms

ga6Law1J5X9T9RW6j9bNdOwzfReedA.ttf

ga6Law1J5X9T9RW6j9bNdOwzfReedA.ttf

1018 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1706 ms

fa-solid-900.woff

fa-solid-900.woff

1650 ms

fa-solid-900.woff

fa-solid-900.woff

2107 ms

fa-regular-400.woff

fa-regular-400.woff

2150 ms

__utm.gif

__utm.gif

76 ms

collect

collect

845 ms

ga-audiences

ga-audiences

260 ms

1eda5a7a-7503-40f8-b490-86979443ba95

1eda5a7a-7503-40f8-b490-86979443ba95

302 ms

wp-polyfill-fetch.min.js

wp-polyfill-fetch.min.js

1056 ms

wp-polyfill-dom-rect.min.js

wp-polyfill-dom-rect.min.js

1398 ms

wp-polyfill-url.min.js

wp-polyfill-url.min.js

1475 ms

wp-polyfill-formdata.min.js

wp-polyfill-formdata.min.js

1877 ms

slate-logo-1.png

slate-logo-1.png

904 ms

slate-logo-light-1.png

slate-logo-light-1.png

21 ms

web-widget-framework-96c2ac7dafdad68c4a30.js

web-widget-framework-96c2ac7dafdad68c4a30.js

43 ms

Accessibility Review

slate.co accessibility score

79

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

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

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

slate.co best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

slate.co SEO score

92

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

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 Slate.co 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 Slate.co 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

slate.co

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