Tools & Wizards About Us
w3w.co screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

w3w.co

what3words /// The simplest way to talk about location

Page Load Speed

1.2 sec in total

First Response

370 ms

Resources Loaded

753 ms

Page Rendered

50 ms

w3w.co screenshot

About Website

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

Every 3 metre square of the world has been given a unique combination of three words. Used for e-commerce and delivery, navigation, emergencies and more.

Visit w3w.co

Key Findings

We analyzed W3w.co page load time and found that the first response time was 370 ms and then it took 803 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

w3w.co performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

what3words.com

370 ms

clip.apples.leap

223 ms

2e9b302bfc62901a.css

8 ms

0ed462b33e066d7f.css

11 ms

e8f9d13873b594fd.css

30 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that all of those requests were addressed to W3w.co and no external sources were called. The less responsive or slowest element that took the longest time to load (370 ms) relates to the external source What3words.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 48.3 kB (65%)

Content Size

74.2 kB

After Optimization

25.9 kB

  • HTML

In fact, the total size of W3w.co main page is 74.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 74.2 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 48.3 kB

  • Original 74.2 kB
  • After minification 74.2 kB
  • After compression 25.9 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 48.3 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (92%)

Requests Now

24

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

what3words.com

what3words.com

370 ms

clip.apples.leap

clip.apples.leap

223 ms

2e9b302bfc62901a.css

2e9b302bfc62901a.css

8 ms

0ed462b33e066d7f.css

0ed462b33e066d7f.css

11 ms

e8f9d13873b594fd.css

e8f9d13873b594fd.css

30 ms

8233e1668534cf5c.css

8233e1668534cf5c.css

30 ms

8a948958d22a7ef0.css

8a948958d22a7ef0.css

15 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

15 ms

5952.de4654de1e905c13.js

5952.de4654de1e905c13.js

43 ms

4872.238a2ac08f3114ee.js

4872.238a2ac08f3114ee.js

43 ms

3987.999274ade4dedc50.js

3987.999274ade4dedc50.js

45 ms

6439.898e137937f39018.js

6439.898e137937f39018.js

44 ms

5560.015ff735b8f8025c.js

5560.015ff735b8f8025c.js

45 ms

ea88be26.ad35eaf363139bbe.js

ea88be26.ad35eaf363139bbe.js

48 ms

9464.256a2de2eaeb1b7f.js

9464.256a2de2eaeb1b7f.js

48 ms

webpack-d4b17f2ed332eb6e.js

webpack-d4b17f2ed332eb6e.js

55 ms

framework-847cdbe141f8ae13.js

framework-847cdbe141f8ae13.js

56 ms

main-660f5dca883606b8.js

main-660f5dca883606b8.js

61 ms

_app-85ba1526790d1b7f.js

_app-85ba1526790d1b7f.js

55 ms

c0d53ec4-27e27a1815097b8a.js

c0d53ec4-27e27a1815097b8a.js

63 ms

71d48f31-fb34b13460f5e910.js

71d48f31-fb34b13460f5e910.js

67 ms

3f2dd09b-56068c7560dd46c0.js

3f2dd09b-56068c7560dd46c0.js

62 ms

1469-556fc3f348770310.js

1469-556fc3f348770310.js

80 ms

%5B...input%5D-fa50068c4782eddc.js

%5B...input%5D-fa50068c4782eddc.js

64 ms

_buildManifest.js

_buildManifest.js

65 ms

_ssgManifest.js

_ssgManifest.js

65 ms

SourceSansPro-Regular.192e5a06.woff

SourceSansPro-Regular.192e5a06.woff

7 ms

SourceSansPro-Light.f8432c23.woff

SourceSansPro-Light.f8432c23.woff

7 ms

SourceSansPro-ExtraLight.6f7969c1.woff

SourceSansPro-ExtraLight.6f7969c1.woff

6 ms

SourceSansPro-Semibold.fc32d394.woff

SourceSansPro-Semibold.fc32d394.woff

4 ms

SourceSansPro-Bold.8e41a8cf.woff

SourceSansPro-Bold.8e41a8cf.woff

6 ms

Accessibility Review

w3w.co accessibility score

84

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

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

w3w.co best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

w3w.co SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise W3w.co can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that W3w.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

w3w.co

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