Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

sway.pw

Sway

Page Load Speed

696 ms in total

First Response

107 ms

Resources Loaded

432 ms

Page Rendered

157 ms

sway.pw screenshot

About Website

Welcome to sway.pw homepage info - get ready to check Sway best content right away, or after learning these important things about sway.pw

Visit sway.pw

Key Findings

We analyzed Sway.pw page load time and found that the first response time was 107 ms and then it took 589 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

sway.pw performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

74/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value440 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

sway.pw

107 ms

thesway.co

116 ms

css

52 ms

swagcss.css

56 ms

2Q-AW1e_taO6pHwMXcXW5w.ttf

25 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 20% of them (1 request) were addressed to the original Sway.pw, 40% (2 requests) were made to Thesway.co and 20% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (116 ms) relates to the external source Thesway.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 441 B (51%)

Content Size

872 B

After Optimization

431 B

In fact, the total size of Sway.pw main page is 872 B. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 493 B which makes up the majority of the site volume.

HTML Optimization

-47%

Potential reduce by 234 B

  • Original 493 B
  • After minification 461 B
  • After compression 259 B

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 234 B or 47% of the original size.

CSS Optimization

-55%

Potential reduce by 207 B

  • Original 379 B
  • After minification 302 B
  • After compression 172 B

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. Sway.pw needs all CSS files to be minified and compressed as it can save up to 207 B or 55% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sway. According to our analytics all requests are already optimized.

Accessibility Review

sway.pw accessibility score

95

Accessibility Issues

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

sway.pw 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

SEO Factors

sway.pw SEO score

92

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sway.pw can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Sway.pw main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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