Tools & Wizards About Us
satw.us screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

satw.us

Scandinavia and the World

Page Load Speed

1.3 sec in total

First Response

281 ms

Resources Loaded

668 ms

Page Rendered

385 ms

satw.us screenshot

About Website

Welcome to satw.us homepage info - get ready to check Satw best content right away, or after learning these important things about satw.us

Because your country is weird too.

Visit satw.us

Key Findings

We analyzed Satw.us page load time and found that the first response time was 281 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

satw.us performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.045

99/100

15%

TTI (Time to Interactive)

Value6.3 s

62/100

10%

Network Requests Diagram

satw.us

281 ms

pre_tumblelog.js

8 ms

jquery-1.9.1.min.js

16 ms

tumblelog_post_message_queue.js

10 ms

stylesheet.css

10 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Satw.us, 23% (7 requests) were made to Assets.tumblr.com and 20% (6 requests) were made to Ap.lijit.com. The less responsive or slowest element that took the longest time to load (281 ms) belongs to the original domain Satw.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 495.8 kB (40%)

Content Size

1.2 MB

After Optimization

751.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Satw.us main page is 1.2 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. 50% of websites need less resources to load. Javascripts take 652.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 34.5 kB

  • Original 43.9 kB
  • After minification 36.0 kB
  • After compression 9.4 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. This page needs HTML code to be minified as it can gain 7.9 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 34.5 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 41.3 kB

  • Original 549.9 kB
  • After minification 508.6 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. Satw images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 419.6 kB

  • Original 652.8 kB
  • After minification 652.8 kB
  • After compression 233.2 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 419.6 kB or 64% of the original size.

CSS Optimization

-59%

Potential reduce by 384 B

  • Original 655 B
  • After minification 655 B
  • After compression 271 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. Satw.us needs all CSS files to be minified and compressed as it can save up to 384 B or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (52%)

Requests Now

29

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

satw.us

satw.us

281 ms

pre_tumblelog.js

pre_tumblelog.js

8 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

16 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

10 ms

stylesheet.css

stylesheet.css

10 ms

fpi.js

fpi.js

4 ms

index.js

index.js

13 ms

ga.js

ga.js

91 ms

tumblr_inline_o4518uVssq1rl8pw7_500.png

tumblr_inline_o4518uVssq1rl8pw7_500.png

252 ms

tumblr_o3ogxwORXe1spdrn0o1_1280.png

tumblr_o3ogxwORXe1spdrn0o1_1280.png

87 ms

sync

sync

71 ms

tumblr_inline_o2l74mAXxg1rl8pw7_400.jpg

tumblr_inline_o2l74mAXxg1rl8pw7_400.jpg

227 ms

impixu

impixu

68 ms

impixu

impixu

27 ms

tumblr_o33xe09DYX1spdrn0o1_1280.jpg

tumblr_o33xe09DYX1spdrn0o1_1280.jpg

27 ms

analytics.html

analytics.html

160 ms

login_check.html

login_check.html

26 ms

adcfg

adcfg

130 ms

adcfg

adcfg

80 ms

__utm.gif

__utm.gif

114 ms

avatar_0f8044bc6b95_40.png

avatar_0f8044bc6b95_40.png

84 ms

addelivery

addelivery

119 ms

iframe_logo.png

iframe_logo.png

37 ms

addelivery

addelivery

63 ms

rapid-3.36.js

rapid-3.36.js

26 ms

rapidworker-1.2.js

rapidworker-1.2.js

29 ms

ga.js

ga.js

54 ms

analytics.js

analytics.js

36 ms

cs.js

cs.js

48 ms

__utm.gif

__utm.gif

14 ms

Accessibility Review

satw.us accessibility score

43

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

satw.us best practices score

77

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

satw.us SEO score

84

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Satw.us 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 Satw.us 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

satw.us

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