Tools & Wizards About Us
shift.how screenshot

Report Summary

  • 77

    Performance

    Renders faster than
    85% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

shift.how

SHiFT: Find your role in tackling ocean plastic pollution

Page Load Speed

4.2 sec in total

First Response

135 ms

Resources Loaded

2.7 sec

Page Rendered

1.3 sec

shift.how screenshot

About Website

Welcome to shift.how homepage info - get ready to check SHiFT best content right away, or after learning these important things about shift.how

Visit shift.how

Key Findings

We analyzed Shift.how page load time and found that the first response time was 135 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

shift.how performance score

77

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

48/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

shift.how

135 ms

shift.how

835 ms

app.css

18 ms

uon1chx.css

108 ms

email-decode.min.js

19 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 64% of them (28 requests) were addressed to the original Shift.how, 32% (14 requests) were made to Use.typekit.net and 2% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Shift.how.

Page Optimization Overview & Recommendations

Page size can be reduced by 44.4 kB (9%)

Content Size

502.5 kB

After Optimization

458.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Shift.how main page is 502.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 412.9 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 15.4 kB

  • Original 21.6 kB
  • After minification 21.3 kB
  • After compression 6.3 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 15.4 kB or 71% of the original size.

Image Optimization

-7%

Potential reduce by 28.5 kB

  • Original 412.9 kB
  • After minification 384.3 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. SHiFT images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 17 B

  • Original 54.4 kB
  • After minification 54.4 kB
  • After compression 54.4 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

-3%

Potential reduce by 445 B

  • Original 13.6 kB
  • After minification 13.6 kB
  • After compression 13.2 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. Shift.how has all CSS files already compressed.

Requests Breakdown

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

Requests Now

29

After Optimization

21

  • Images
  • JavaScript
  • CSS

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SHiFT. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

shift.how

shift.how

135 ms

shift.how

shift.how

835 ms

app.css

app.css

18 ms

uon1chx.css

uon1chx.css

108 ms

email-decode.min.js

email-decode.min.js

19 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

37 ms

framework-extras.js

framework-extras.js

43 ms

framework-extras.css

framework-extras.css

29 ms

app.js

app.js

45 ms

rocket-loader.min.js

rocket-loader.min.js

21 ms

img_5f42fed82e0fb1142671f15228b67272.jpg

img_5f42fed82e0fb1142671f15228b67272.jpg

450 ms

img_99c70ff819d7c7ca743f9508fd341f11.jpg

img_99c70ff819d7c7ca743f9508fd341f11.jpg

470 ms

img_5378e3a75da04696c270b71dfcc0db96.jpg

img_5378e3a75da04696c270b71dfcc0db96.jpg

476 ms

img_2d6a7be1ccea68ce165c7760f50e1266.jpg

img_2d6a7be1ccea68ce165c7760f50e1266.jpg

498 ms

img_ddf295c579bfe825d134a8118a109880.jpg

img_ddf295c579bfe825d134a8118a109880.jpg

469 ms

img_9251d628603bf0c7b6de78618d7e2320.jpg

img_9251d628603bf0c7b6de78618d7e2320.jpg

498 ms

img_97e74af0ccf86685cad730d03affde44.jpg

img_97e74af0ccf86685cad730d03affde44.jpg

893 ms

img_d759791e75f0678881e3bd359618485d.jpg

img_d759791e75f0678881e3bd359618485d.jpg

916 ms

img_2fcd0e8a2da47f3899b11e22cc0da10b.jpg

img_2fcd0e8a2da47f3899b11e22cc0da10b.jpg

910 ms

img_7cd034cc82c9981dd84868a618f23b8e.jpg

img_7cd034cc82c9981dd84868a618f23b8e.jpg

926 ms

img_49b601fd1fc15c91abcc10c8dec83389.jpg

img_49b601fd1fc15c91abcc10c8dec83389.jpg

945 ms

img_451421ab1ba3ff5b6b05c7d5df722e79.jpg

img_451421ab1ba3ff5b6b05c7d5df722e79.jpg

951 ms

img_258f2eadbdf947367c2fd75a2ad8b9fe.jpg

img_258f2eadbdf947367c2fd75a2ad8b9fe.jpg

1331 ms

img_43ccb3a9125776c7da0c67b03aaeff77.jpg

img_43ccb3a9125776c7da0c67b03aaeff77.jpg

1353 ms

img_840ccd4def0e98dc85e7e6465efa902b.jpg

img_840ccd4def0e98dc85e7e6465efa902b.jpg

1341 ms

img_6094902f7c9c5d73643d5ebdf15fb293.jpg

img_6094902f7c9c5d73643d5ebdf15fb293.jpg

1353 ms

p.css

p.css

20 ms

2ccb8bf9110f090f5b68.svg

2ccb8bf9110f090f5b68.svg

1249 ms

fdd56603d8676d5514c8.svg

fdd56603d8676d5514c8.svg

1248 ms

64985efbc99c43cad2b8.svg

64985efbc99c43cad2b8.svg

1613 ms

d

d

4 ms

d

d

10 ms

d

d

10 ms

d

d

14 ms

d

d

12 ms

d

d

13 ms

d

d

23 ms

d

d

13 ms

d

d

23 ms

d

d

24 ms

d

d

24 ms

d

d

21 ms

d

d

24 ms

framework-extras.js

framework-extras.js

22 ms

Accessibility Review

shift.how accessibility score

73

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

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

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

shift.how 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

shift.how SEO score

76

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

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 Shift.how 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 Shift.how 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

shift.how

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