Tools & Wizards About Us
no-tar-sands.org screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

no-tar-sands.org

No Tar Sands | The UK Tar Sands Network campaigns in partnership

Page Load Speed

2.9 sec in total

First Response

49 ms

Resources Loaded

2.7 sec

Page Rendered

180 ms

no-tar-sands.org screenshot

About Website

Welcome to no-tar-sands.org homepage info - get ready to check No Tar Sands best content right away, or after learning these important things about no-tar-sands.org

The UK Tar Sands Network campaigns in partnership with Indigenous communities affected by the Tar Sands oil developments in Canada.

Visit no-tar-sands.org

Key Findings

We analyzed No-tar-sands.org page load time and found that the first response time was 49 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

no-tar-sands.org performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.284

42/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

no-tar-sands.org

49 ms

www.no-tar-sands.org

564 ms

webfont.js

108 ms

p_d4__cssminify_yes.css

585 ms

wqtnptxmachnun6i4965q__gwfxxbtkpw9k_.js

525 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 78% of them (28 requests) were addressed to the original No-tar-sands.org, 6% (2 requests) were made to Use.typekit.net and 3% (1 request) were made to . The less responsive or slowest element that took the longest time to load (598 ms) belongs to the original domain No-tar-sands.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 86.4 kB (5%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 62.1 kB

  • Original 81.3 kB
  • After minification 79.5 kB
  • After compression 19.2 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 62.1 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 1.3 kB

  • Original 1.3 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. No Tar Sands images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 15.8 kB

  • Original 124.7 kB
  • After minification 124.7 kB
  • After compression 108.9 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 15.8 kB or 13% of the original size.

CSS Optimization

-6%

Potential reduce by 7.3 kB

  • Original 123.2 kB
  • After minification 115.9 kB
  • After compression 115.9 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. No-tar-sands.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (48%)

Requests Now

27

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

no-tar-sands.org

no-tar-sands.org

49 ms

www.no-tar-sands.org

www.no-tar-sands.org

564 ms

webfont.js

webfont.js

108 ms

p_d4__cssminify_yes.css

p_d4__cssminify_yes.css

585 ms

wqtnptxmachnun6i4965q__gwfxxbtkpw9k_.js

wqtnptxmachnun6i4965q__gwfxxbtkpw9k_.js

525 ms

_custom-css_1_csblog_7zrfl_cscache_6_csrev_28.css

_custom-css_1_csblog_7zrfl_cscache_6_csrev_28.css

370 ms

style.min.css

style.min.css

427 ms

style.css

style.css

172 ms

gprofiles.js

gprofiles.js

284 ms

wpgroho.js

wpgroho.js

395 ms

jetpack-carousel_m_1576278967j_cssminify_yes.css

jetpack-carousel_m_1576278967j_cssminify_yes.css

475 ms

bm1aga92dfverpzrsttwbzfmv1_5w__.js

bm1aga92dfverpzrsttwbzfmv1_5w__.js

598 ms

w.js

w.js

531 ms

kza1omf.js

kza1omf.js

87 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

324 ms

css

css

242 ms

uktarsandslogo15.png

uktarsandslogo15.png

124 ms

6d1a21012.jpg

6d1a21012.jpg

429 ms

agm-2016-022.jpg

agm-2016-022.jpg

444 ms

danieltotal-e14497782187342.jpg

danieltotal-e14497782187342.jpg

279 ms

kayak2.jpg

kayak2.jpg

279 ms

eriel2.png

eriel2.png

349 ms

trans.png

trans.png

219 ms

6d1a21182.jpg

6d1a21182.jpg

396 ms

oil-profit-logo-300x124.jpg

oil-profit-logo-300x124.jpg

380 ms

screenshot-from-2017-10-14-15-38-141.png

screenshot-from-2017-10-14-15-38-141.png

386 ms

xXNJVVHOV949t+t7a+h8qJiExAAA=

xXNJVVHOV949t+t7a+h8qJiExAAA=

9 ms

d

d

8 ms

wp-polyfill-fetch.min.js

wp-polyfill-fetch.min.js

33 ms

wp-polyfill-formdata.min.js

wp-polyfill-formdata.min.js

33 ms

wp-polyfill-element-closest.min.js

wp-polyfill-element-closest.min.js

36 ms

hovercard.min.css

hovercard.min.css

412 ms

services.min.css

services.min.css

447 ms

remote-login.php

remote-login.php

61 ms

p.gif

p.gif

31 ms

g.gif

g.gif

209 ms

Accessibility Review

no-tar-sands.org accessibility score

93

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-hidden="true"] elements contain focusable descendents

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.

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

no-tar-sands.org best practices score

67

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

Browser errors were logged to the console

SEO Factors

no-tar-sands.org SEO score

93

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

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 No-tar-sands.org 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 No-tar-sands.org 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

no-tar-sands.org

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