Tools & Wizards About Us
day-by-day.org screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

day-by-day.org

Day By Day: Gateway to the Work of Hazelden Author Shelly Marshall

Page Load Speed

991 ms in total

First Response

51 ms

Resources Loaded

450 ms

Page Rendered

490 ms

day-by-day.org screenshot

About Website

Visit day-by-day.org now to see the best up-to-date Day By content and also check out these interesting facts you probably never knew about day-by-day.org

This is the connection site for the work of Shelly Marshall. She is devoted to the recovery of the young chemical dependent, their families and you. Are you a parent, sponsor or sponsee? Do you work i...

Visit day-by-day.org

Key Findings

We analyzed Day-by-day.org page load time and found that the first response time was 51 ms and then it took 940 ms 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

day-by-day.org performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

day-by-day.org

51 ms

main.css

21 ms

adsbygoogle.js

55 ms

jquery.min.js

95 ms

jquery.dropotron.min.js

38 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 82% of them (28 requests) were addressed to the original Day-by-day.org, 3% (1 request) were made to Pagead2.googlesyndication.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (211 ms) belongs to the original domain Day-by-day.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 22.0 kB (2%)

Content Size

1.2 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Day-by-day.org 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. 35% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 17.0 kB

  • Original 22.9 kB
  • After minification 20.4 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 2.5 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 17.0 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 1.7 kB

  • Original 1.0 MB
  • After minification 1.0 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. Day By images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.0 kB

  • Original 109.9 kB
  • After minification 109.9 kB
  • After compression 107.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

-9%

Potential reduce by 1.3 kB

  • Original 13.7 kB
  • After minification 13.7 kB
  • After compression 12.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. Day-by-day.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (57%)

Requests Now

30

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

day-by-day.org

day-by-day.org

51 ms

main.css

main.css

21 ms

adsbygoogle.js

adsbygoogle.js

55 ms

jquery.min.js

jquery.min.js

95 ms

jquery.dropotron.min.js

jquery.dropotron.min.js

38 ms

jquery.scrolly.min.js

jquery.scrolly.min.js

41 ms

jquery.scrollgress.min.js

jquery.scrollgress.min.js

40 ms

skel.min.js

skel.min.js

41 ms

util.js

util.js

94 ms

main.js

main.js

95 ms

ps1.jpg

ps1.jpg

211 ms

Lee.jpg

Lee.jpg

210 ms

DayByDay.jpg

DayByDay.jpg

209 ms

Walksoftly473-1.jpg

Walksoftly473-1.jpg

95 ms

YSF473.jpg

YSF473.jpg

210 ms

pic1.jpg

pic1.jpg

209 ms

font-awesome.min.css

font-awesome.min.css

80 ms

css

css

20 ms

uwt.js

uwt.js

94 ms

light-bl.svg

light-bl.svg

24 ms

light-br.svg

light-br.svg

26 ms

overlay1.png

overlay1.png

26 ms

banner.jpg

banner.jpg

170 ms

dark-tl.svg

dark-tl.svg

24 ms

dark-tr.svg

dark-tr.svg

26 ms

dark-bl.svg

dark-bl.svg

41 ms

dark-br.svg

dark-br.svg

41 ms

overlay.png

overlay.png

43 ms

light-tl.svg

light-tl.svg

45 ms

light-tr.svg

light-tr.svg

44 ms

font

font

83 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

69 ms

adsct

adsct

61 ms

adsct

adsct

161 ms

Accessibility Review

day-by-day.org accessibility score

77

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.

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

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

day-by-day.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

day-by-day.org SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

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

day-by-day.org

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