Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

nexav.org

News and Information for People Over 50 | Next Avenue

Page Load Speed

3 sec in total

First Response

70 ms

Resources Loaded

2.4 sec

Page Rendered

577 ms

nexav.org screenshot

About Website

Visit nexav.org now to see the best up-to-date Nexav content for United States and also check out these interesting facts you probably never knew about nexav.org

Find news, advice, information, conversations and stories curated for people over 50 on Next Avenue. We are the only national public media journalism service for baby boomers and seniors.

Visit nexav.org

Key Findings

We analyzed Nexav.org page load time and found that the first response time was 70 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

nexav.org performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value6.7 s

35/100

10%

TBT (Total Blocking Time)

Value1,910 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

nexav.org

70 ms

www.nextavenue.org

219 ms

4e9330042da601523e8d.css

21 ms

brothersstory.cover.1231x800.jpg

777 ms

polyfills-db0d1cb181866800bd64.js

36 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Nexav.org, 38% (26 requests) were made to Nextavenue.org and 20% (14 requests) were made to Img.tpt.cloud. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Img.tpt.cloud.

Page Optimization Overview & Recommendations

Page size can be reduced by 584.5 kB (26%)

Content Size

2.2 MB

After Optimization

1.6 MB

In fact, the total size of Nexav.org main page is 2.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. 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. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 117.0 kB

  • Original 147.0 kB
  • After minification 147.0 kB
  • After compression 30.0 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 117.0 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 12.9 kB

  • Original 1.1 MB
  • After minification 1.1 MB

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. Nexav images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 454.4 kB

  • Original 934.2 kB
  • After minification 934.1 kB
  • After compression 479.7 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 454.4 kB or 49% of the original size.

CSS Optimization

-11%

Potential reduce by 134 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 1.1 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. Nexav.org needs all CSS files to be minified and compressed as it can save up to 134 B or 11% of the original size.

Requests Breakdown

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

Requests Now

61

After Optimization

27

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

Accessibility Review

nexav.org accessibility score

83

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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.

Best Practices

nexav.org best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

nexav.org SEO score

86

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

Links do not have descriptive text

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

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 Nexav.org 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 Nexav.org 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

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