Tools & Wizards About Us
without-warning.net screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

without-warning.net

Early onset Alzheimer's support program | Without Warning

Page Load Speed

1.8 sec in total

First Response

36 ms

Resources Loaded

1.6 sec

Page Rendered

237 ms

without-warning.net screenshot

About Website

Click here to check amazing Without Warning content. Otherwise, check out these important facts you probably never knew about without-warning.net

Without Warning is a support program for families living with early onset Alzheimer's disease developed by the Rush Alzheimer's Disease Center.

Visit without-warning.net

Key Findings

We analyzed Without-warning.net page load time and found that the first response time was 36 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

without-warning.net performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

without-warning.net

36 ms

withoutwarning.net

108 ms

withoutwarning.net

170 ms

www.withoutwarning.net

557 ms

js

52 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Without-warning.net, 81% (52 requests) were made to Withoutwarning.net and 14% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (557 ms) relates to the external source Withoutwarning.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 64.8 kB (9%)

Content Size

707.1 kB

After Optimization

642.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Without-warning.net main page is 707.1 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. Images take 585.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 19.8 kB

  • Original 25.5 kB
  • After minification 22.8 kB
  • After compression 5.7 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 2.7 kB, which is 11% 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 19.8 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 33.4 kB

  • Original 585.6 kB
  • After minification 552.2 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. Without Warning images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 6.3 kB

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

CSS Optimization

-24%

Potential reduce by 5.3 kB

  • Original 22.1 kB
  • After minification 20.8 kB
  • After compression 16.8 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. Without-warning.net needs all CSS files to be minified and compressed as it can save up to 5.3 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (90%)

Requests Now

51

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

without-warning.net

without-warning.net

36 ms

withoutwarning.net

withoutwarning.net

108 ms

withoutwarning.net

withoutwarning.net

170 ms

www.withoutwarning.net

www.withoutwarning.net

557 ms

js

js

52 ms

superfish.css

superfish.css

38 ms

align.module.css

align.module.css

71 ms

fieldgroup.module.css

fieldgroup.module.css

103 ms

container-inline.module.css

container-inline.module.css

128 ms

clearfix.module.css

clearfix.module.css

143 ms

details.module.css

details.module.css

137 ms

hidden.module.css

hidden.module.css

135 ms

item-list.module.css

item-list.module.css

143 ms

js.module.css

js.module.css

144 ms

nowrap.module.css

nowrap.module.css

167 ms

position-container.module.css

position-container.module.css

191 ms

reset-appearance.module.css

reset-appearance.module.css

191 ms

resize.module.css

resize.module.css

190 ms

system-status-counter.css

system-status-counter.css

217 ms

system-status-report-counters.css

system-status-report-counters.css

167 ms

system-status-report-general-info.css

system-status-report-general-info.css

206 ms

tablesort.module.css

tablesort.module.css

190 ms

views.module.css

views.module.css

229 ms

responsive_menu_breakpoint.css

responsive_menu_breakpoint.css

215 ms

responsive_menu.css

responsive_menu.css

261 ms

mmenu.css

mmenu.css

262 ms

mmenu.bootstrap.css

mmenu.bootstrap.css

265 ms

extlink.css

extlink.css

260 ms

reset.css

reset.css

263 ms

base.css

base.css

268 ms

rye.css

rye.css

299 ms

forms.css

forms.css

325 ms

messages.css

messages.css

323 ms

tabs.css

tabs.css

286 ms

css

css

30 ms

logo-ww.png

logo-ww.png

386 ms

logo_gmi.png

logo_gmi.png

387 ms

jquery.min.js

jquery.min.js

375 ms

once.min.js

once.min.js

374 ms

drupalSettingsLoader.js

drupalSettingsLoader.js

383 ms

drupal.js

drupal.js

384 ms

drupal.init.js

drupal.init.js

385 ms

mmenu.js

mmenu.js

359 ms

responsive_menu.config.js

responsive_menu.config.js

349 ms

responsive_menu.bootstrap.js

responsive_menu.bootstrap.js

318 ms

google_analytics.js

google_analytics.js

324 ms

extlink.js

extlink.js

317 ms

superfish.js

superfish.js

313 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

286 ms

sfsmallscreen.js

sfsmallscreen.js

310 ms

supposition.js

supposition.js

311 ms

supersubs.js

supersubs.js

286 ms

superfish.js

superfish.js

322 ms

social_circles.jpg

social_circles.jpg

332 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

20 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

30 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

38 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

44 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

46 ms

S6u9w4BMUTPHh50XSwiPHw.woff

S6u9w4BMUTPHh50XSwiPHw.woff

45 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

46 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

45 ms

S6u8w4BMUTPHh30AXC-s.woff

S6u8w4BMUTPHh30AXC-s.woff

44 ms

print.css

print.css

31 ms

Accessibility Review

without-warning.net accessibility score

88

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

Best Practices

without-warning.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

Page has valid source maps

SEO Factors

without-warning.net SEO score

86

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

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 Without-warning.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 Without-warning.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

without-warning.net

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