Tools & Wizards About Us
napost.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

napost.com

Seattle Japanese Community News | The North American Post

Page Load Speed

9.3 sec in total

First Response

345 ms

Resources Loaded

8.7 sec

Page Rendered

219 ms

napost.com screenshot

About Website

Welcome to napost.com homepage info - get ready to check Na Post best content right away, or after learning these important things about napost.com

The North American Post has served Seattle's Japanese Community since 1902. Our articles are all about Japanese in Seattle, including Japanese and Japanese American community news, Japanese relat...

Visit napost.com

Key Findings

We analyzed Napost.com page load time and found that the first response time was 345 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

napost.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

napost.com

345 ms

js

90 ms

mediaelementplayer-legacy.min.css

35 ms

wp-mediaelement.min.css

36 ms

frontend.min.css

125 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 69% of them (22 requests) were addressed to the original Napost.com, 19% (6 requests) were made to C0.wp.com and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (417 ms) belongs to the original domain Napost.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 323.2 kB (52%)

Content Size

618.5 kB

After Optimization

295.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Napost.com main page is 618.5 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. 50% of websites need less resources to load. HTML takes 281.7 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 250.2 kB

  • Original 281.7 kB
  • After minification 264.0 kB
  • After compression 31.5 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 250.2 kB or 89% of the original size.

JavaScript Optimization

-9%

Potential reduce by 16.6 kB

  • Original 182.5 kB
  • After minification 181.9 kB
  • After compression 165.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. This website has mostly compressed JavaScripts.

CSS Optimization

-37%

Potential reduce by 56.5 kB

  • Original 154.4 kB
  • After minification 136.3 kB
  • After compression 97.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. Napost.com needs all CSS files to be minified and compressed as it can save up to 56.5 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (87%)

Requests Now

30

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

napost.com

napost.com

345 ms

js

js

90 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

35 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

36 ms

frontend.min.css

frontend.min.css

125 ms

flatpickr.min.css

flatpickr.min.css

191 ms

select2.min.css

select2.min.css

138 ms

style.css

style.css

139 ms

css

css

47 ms

default.css

default.css

192 ms

tds-front.css

tds-front.css

206 ms

style.css

style.css

292 ms

td_legacy_main.css

td_legacy_main.css

271 ms

td_legacy_subscription.css

td_legacy_subscription.css

214 ms

frontend-gtag.min.js

frontend-gtag.min.js

217 ms

jquery.min.js

jquery.min.js

9 ms

jquery-migrate.min.js

jquery-migrate.min.js

6 ms

flatpickr.min.js

flatpickr.min.js

317 ms

select2.min.js

select2.min.js

270 ms

lazysizes.min.js

lazysizes.min.js

309 ms

postviews-cache.js

postviews-cache.js

309 ms

frontend.min.js

frontend.min.js

413 ms

tagdiv_theme.min.js

tagdiv_theme.min.js

417 ms

comment-reply.min.js

comment-reply.min.js

6 ms

underscore-before.js

underscore-before.js

414 ms

underscore.min.js

underscore.min.js

11 ms

underscore-after.js

underscore-after.js

415 ms

js_files_for_front.min.js

js_files_for_front.min.js

415 ms

e-202436.js

e-202436.js

39 ms

newsmag.svg

newsmag.svg

72 ms

newsmag.woff

newsmag.woff

131 ms

font

font

36 ms

Accessibility Review

napost.com accessibility score

76

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

napost.com 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

SEO Factors

napost.com SEO score

91

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

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

napost.com

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