Tools & Wizards About Us
sainttimothysdanville.org screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

sainttimothysdanville.org

ST. TIMOTHY'S | DANVILLE - Home

Page Load Speed

2.8 sec in total

First Response

126 ms

Resources Loaded

2.2 sec

Page Rendered

479 ms

sainttimothysdanville.org screenshot

About Website

Visit sainttimothysdanville.org now to see the best up-to-date Saint TIMOTHY S DANVILLE content for United States and also check out these interesting facts you probably never knew about sainttimothysdanville.org

progressive episcopal church in Danville California

Visit sainttimothysdanville.org

Key Findings

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

Performance Metrics

sainttimothysdanville.org performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value2,520 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value23.1 s

1/100

10%

Network Requests Diagram

sainttimothysdanville.org

126 ms

www.sainttimothysdanville.org

127 ms

www.sainttimothysdanville.org

230 ms

sites.css

36 ms

fancybox.css

35 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 27% of them (24 requests) were addressed to the original Sainttimothysdanville.org, 37% (33 requests) were made to Cdn2.editmysite.com and 18% (16 requests) were made to Inffuse-calendar2.appspot.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Sainttimothysdanville.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 349.7 kB (11%)

Content Size

3.3 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sainttimothysdanville.org main page is 3.3 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. 75% 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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 127.2 kB

  • Original 145.8 kB
  • After minification 142.9 kB
  • After compression 18.6 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 127.2 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 16.8 kB

  • Original 2.3 MB
  • After minification 2.2 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. Saint TIMOTHY S DANVILLE images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 201.6 kB

  • Original 865.1 kB
  • After minification 864.5 kB
  • After compression 663.5 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 201.6 kB or 23% of the original size.

CSS Optimization

-8%

Potential reduce by 4.1 kB

  • Original 52.4 kB
  • After minification 52.4 kB
  • After compression 48.3 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. Sainttimothysdanville.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 43 (61%)

Requests Now

71

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sainttimothysdanville.org

sainttimothysdanville.org

126 ms

www.sainttimothysdanville.org

www.sainttimothysdanville.org

127 ms

www.sainttimothysdanville.org

www.sainttimothysdanville.org

230 ms

sites.css

sites.css

36 ms

fancybox.css

fancybox.css

35 ms

social-icons.css

social-icons.css

31 ms

main_style.css

main_style.css

337 ms

font.css

font.css

33 ms

font.css

font.css

33 ms

font.css

font.css

49 ms

font.css

font.css

50 ms

font.css

font.css

51 ms

slideshow.css

slideshow.css

52 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

53 ms

stl.js

stl.js

51 ms

main.js

main.js

55 ms

slideshow-jq.js

slideshow-jq.js

53 ms

email-decode.min.js

email-decode.min.js

25 ms

footerSignup.js

footerSignup.js

51 ms

plugins.js

plugins.js

98 ms

custom.js

custom.js

388 ms

main-customer-accounts-site.js

main-customer-accounts-site.js

9 ms

footer-toast-published-image-1.png

footer-toast-published-image-1.png

24 ms

instafacw-002.png

instafacw-002.png

494 ms

instafacw-001.png

instafacw-001.png

58 ms

coa-illustration-cross-triquetra-svg_1.png

coa-illustration-cross-triquetra-svg_1.png

57 ms

helping-hands-512_1.png

helping-hands-512_1.png

494 ms

heart_5.png

heart_5.png

494 ms

welcome-001.png

welcome-001.png

492 ms

shield-001.png

shield-001.png

493 ms

shield-002.png

shield-002.png

492 ms

light.woff

light.woff

34 ms

regular.woff

regular.woff

34 ms

bold.woff

bold.woff

33 ms

regular.woff

regular.woff

31 ms

bold.woff

bold.woff

32 ms

widget.html

widget.html

73 ms

1668046025.jpg

1668046025.jpg

555 ms

regular.woff

regular.woff

24 ms

bold.woff

bold.woff

25 ms

italic.woff

italic.woff

22 ms

bolditalic.woff

bolditalic.woff

24 ms

353257211.jpeg

353257211.jpeg

1287 ms

regular.woff

regular.woff

16 ms

bold.woff

bold.woff

17 ms

jquery.min.js

jquery.min.js

425 ms

angular.min.js

angular.min.js

444 ms

angular-translate.min.js

angular-translate.min.js

371 ms

css

css

489 ms

css

css

523 ms

css

css

528 ms

icon

icon

527 ms

widget.css

widget.css

422 ms

inffuse.js

inffuse.js

529 ms

external.js

external.js

421 ms

internal.js

internal.js

460 ms

recurring.js

recurring.js

487 ms

mixed.js

mixed.js

419 ms

manager.js

manager.js

420 ms

analyt.js

analyt.js

486 ms

constants.js

constants.js

486 ms

ab.js

ab.js

439 ms

widget.js

widget.js

487 ms

chroma.js

chroma.js

520 ms

moment.js

moment.js

519 ms

moment-timezone.js

moment-timezone.js

539 ms

ga.js

ga.js

236 ms

snowday262.js

snowday262.js

129 ms

free-footer-v3.css

free-footer-v3.css

60 ms

781 ms

img-7627_orig.jpg

img-7627_orig.jpg

784 ms

grace_orig.jpg

grace_orig.jpg

811 ms

game-night_orig.jpg

game-night_orig.jpg

611 ms

noah_orig.jpeg

noah_orig.jpeg

727 ms

john_orig.jpg

john_orig.jpg

625 ms

earth_orig.jpg

earth_orig.jpg

853 ms

control_icons.gif

control_icons.gif

58 ms

loading.gif

loading.gif

57 ms

logotype.svg

logotype.svg

74 ms

sqmarket-medium.woff

sqmarket-medium.woff

15 ms

flUhRq6tzZclQEJ-Vdg-IuiaDsNaIhQ8tQ.woff

flUhRq6tzZclQEJ-Vdg-IuiaDsNaIhQ8tQ.woff

39 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQXjM.woff

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQUwaEQXjM.woff

59 ms

data

data

299 ms

tp2

tp2

143 ms

mixpanel-2.min.js

mixpanel-2.min.js

44 ms

main.js

main.js

147 ms

34 ms

38 ms

53 ms

Accessibility Review

sainttimothysdanville.org accessibility score

94

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

<frame> or <iframe> elements do not have a title

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

sainttimothysdanville.org best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

sainttimothysdanville.org SEO score

85

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

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 Sainttimothysdanville.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 Sainttimothysdanville.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

sainttimothysdanville.org

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