Tools & Wizards About Us
seattle.net screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

seattle.net

Home | Seattle.net

Page Load Speed

3.5 sec in total

First Response

1.1 sec

Resources Loaded

1.7 sec

Page Rendered

678 ms

seattle.net screenshot

About Website

Click here to check amazing Seattle content. Otherwise, check out these important facts you probably never knew about seattle.net

Things to do in Seattle. A growing, curated list of some of the best the city has to offer. Visiting Seattle? This directory should set your planning in the right direction.

Visit seattle.net

Key Findings

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

Performance Metrics

seattle.net performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value3,330 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

seattle.net

1109 ms

style.css

203 ms

styles.css

155 ms

show_ads.js

15 ms

jquery.min.js

32 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 41% of them (7 requests) were addressed to the original Seattle.net, 24% (4 requests) were made to Pagead2.googlesyndication.com and 18% (3 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Seattle.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 194.6 kB (67%)

Content Size

288.6 kB

After Optimization

94.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Seattle.net main page is 288.6 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. HTML takes 139.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 106.6 kB

  • Original 139.8 kB
  • After minification 136.2 kB
  • After compression 33.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 106.6 kB or 76% of the original size.

JavaScript Optimization

-50%

Potential reduce by 54.7 kB

  • Original 109.0 kB
  • After minification 107.8 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 54.7 kB or 50% of the original size.

CSS Optimization

-84%

Potential reduce by 33.4 kB

  • Original 39.8 kB
  • After minification 27.2 kB
  • After compression 6.4 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. Seattle.net needs all CSS files to be minified and compressed as it can save up to 33.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (56%)

Requests Now

16

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

seattle.net

seattle.net

1109 ms

style.css

style.css

203 ms

styles.css

styles.css

155 ms

show_ads.js

show_ads.js

15 ms

jquery.min.js

jquery.min.js

32 ms

nicescroll.js

nicescroll.js

398 ms

hdi.js

hdi.js

139 ms

jquery.form.min.js

jquery.form.min.js

397 ms

scripts.js

scripts.js

381 ms

ca-pub-1718862262644502.js

ca-pub-1718862262644502.js

397 ms

zrt_lookup.html

zrt_lookup.html

388 ms

show_ads_impl.js

show_ads_impl.js

343 ms

ga.js

ga.js

123 ms

ads

ads

48 ms

osd.js

osd.js

21 ms

__utm.gif

__utm.gif

31 ms

ads

ads

23 ms

Accessibility Review

seattle.net accessibility score

96

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.

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

seattle.net 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

Missing source maps for large first-party JavaScript

SEO Factors

seattle.net SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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 Seattle.net 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 Seattle.net 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

seattle.net

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: