Tools & Wizards About Us
obitsarchive.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

obitsarchive.com

Page Load Speed

1.7 sec in total

First Response

411 ms

Resources Loaded

1 sec

Page Rendered

266 ms

obitsarchive.com screenshot

About Website

Click here to check amazing Obitsarchive content for United States. Otherwise, check out these important facts you probably never knew about obitsarchive.com

Search an archive of newspaper obituaries and death notices from hundreds of newspapers. Each newspaper obituary or death notice is indexed by name of the deceased to make searching easier and more pr...

Visit obitsarchive.com

Key Findings

We analyzed Obitsarchive.com page load time and found that the first response time was 411 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

obitsarchive.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

obitsarchive.com

411 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

28 ms

css_r08xPzrQ7fSqA5FJIYypHdfs_8-WiOcQFjKdpWOPqJU.css

37 ms

css_1O_FsY0OGm9dEe_B2oQbLOsKwdeVWgdW3SJ7xPUXRp0.css

35 ms

bootstrap.min.css

7 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 51% of them (22 requests) were addressed to the original Obitsarchive.com, 19% (8 requests) were made to Fonts.gstatic.com and 7% (3 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (411 ms) belongs to the original domain Obitsarchive.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 397.1 kB (66%)

Content Size

604.5 kB

After Optimization

207.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Obitsarchive.com main page is 604.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. CSS take 245.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 43.6 kB

  • Original 53.1 kB
  • After minification 43.2 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 9.8 kB, which is 19% 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 43.6 kB or 82% of the original size.

Image Optimization

-20%

Potential reduce by 27.4 kB

  • Original 135.5 kB
  • After minification 108.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. Obviously, Obitsarchive needs image optimization as it can save up to 27.4 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 123.0 kB

  • Original 170.4 kB
  • After minification 135.2 kB
  • After compression 47.3 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 123.0 kB or 72% of the original size.

CSS Optimization

-83%

Potential reduce by 203.1 kB

  • Original 245.5 kB
  • After minification 242.9 kB
  • After compression 42.5 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. Obitsarchive.com needs all CSS files to be minified and compressed as it can save up to 203.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (68%)

Requests Now

31

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

obitsarchive.com

obitsarchive.com

411 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

28 ms

css_r08xPzrQ7fSqA5FJIYypHdfs_8-WiOcQFjKdpWOPqJU.css

css_r08xPzrQ7fSqA5FJIYypHdfs_8-WiOcQFjKdpWOPqJU.css

37 ms

css_1O_FsY0OGm9dEe_B2oQbLOsKwdeVWgdW3SJ7xPUXRp0.css

css_1O_FsY0OGm9dEe_B2oQbLOsKwdeVWgdW3SJ7xPUXRp0.css

35 ms

bootstrap.min.css

bootstrap.min.css

7 ms

css_Bq6GmCRRuN9fbypLJuWtq-B-c5CnVoyv0AuF1OTEx68.css

css_Bq6GmCRRuN9fbypLJuWtq-B-c5CnVoyv0AuF1OTEx68.css

38 ms

css_Octc3wdVYRZPEa-Ahl2W_9YDf46zZDTAeMy4NILYKvA.css

css_Octc3wdVYRZPEa-Ahl2W_9YDf46zZDTAeMy4NILYKvA.css

30 ms

jquery.min.js

jquery.min.js

37 ms

js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js

js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js

42 ms

js__nSgx_GfdcetKnLamisWPlOyHJrpZ_NiOhXcq2OyN7o.js

js__nSgx_GfdcetKnLamisWPlOyHJrpZ_NiOhXcq2OyN7o.js

51 ms

js_AR0dRK9lH1Z9b5yf4nCtfvKq-5--GSROf2L6Joj1uKE.js

js_AR0dRK9lH1Z9b5yf4nCtfvKq-5--GSROf2L6Joj1uKE.js

43 ms

js_KBA2wnj5G8PmBHKVzQoW_sbYEdpvGZF9PejlXy98voE.js

js_KBA2wnj5G8PmBHKVzQoW_sbYEdpvGZF9PejlXy98voE.js

43 ms

bootstrap.min.js

bootstrap.min.js

13 ms

css

css

25 ms

gtm.js

gtm.js

112 ms

Obits-logo-original.png

Obits-logo-original.png

109 ms

menu-leaf.png

menu-leaf.png

41 ms

menu-expanded.png

menu-expanded.png

40 ms

oa-hp-background-01.jpg

oa-hp-background-01.jpg

61 ms

blusa.png

blusa.png

48 ms

chicago-tribune-featured-icon.png

chicago-tribune-featured-icon.png

40 ms

star-ledger-featured-icon-bw.png

star-ledger-featured-icon-bw.png

41 ms

star-tribune-featured-icon-bw.png

star-tribune-featured-icon-bw.png

41 ms

SF-Chronicle-Box.png

SF-Chronicle-Box.png

43 ms

Houston-Chronicle-4.png

Houston-Chronicle-4.png

45 ms

florida-times-union.png

florida-times-union.png

45 ms

obits-archive-logo-white.png

obits-archive-logo-white.png

58 ms

xozscpT2726on7jbcb_pAj8E0i7KZn-EPnyo3HZu7kw.woff

xozscpT2726on7jbcb_pAj8E0i7KZn-EPnyo3HZu7kw.woff

42 ms

DXI1ORHCpsQm3Vp6mXoaTcZTcY6RJTMCp6-nlHd6HxI.woff

DXI1ORHCpsQm3Vp6mXoaTcZTcY6RJTMCp6-nlHd6HxI.woff

45 ms

MTP_ySUJH_bn48VBG8sNSsZTcY6RJTMCp6-nlHd6HxI.woff

MTP_ySUJH_bn48VBG8sNSsZTcY6RJTMCp6-nlHd6HxI.woff

59 ms

k3k702ZOKiLJc3WVjuplzMZTcY6RJTMCp6-nlHd6HxI.woff

k3k702ZOKiLJc3WVjuplzMZTcY6RJTMCp6-nlHd6HxI.woff

59 ms

xjAJXh38I15wypJXxuGMBn6qoo8ILXpvSLO10ucU3yI.woff

xjAJXh38I15wypJXxuGMBn6qoo8ILXpvSLO10ucU3yI.woff

59 ms

PRmiXeptR36kaC0GEAetxnCwtIq-jb_7MtFG0JFv1Zo.woff

PRmiXeptR36kaC0GEAetxnCwtIq-jb_7MtFG0JFv1Zo.woff

59 ms

PRmiXeptR36kaC0GEAetxhY7anK-GaqvhoRdDPyeRYw.woff

PRmiXeptR36kaC0GEAetxhY7anK-GaqvhoRdDPyeRYw.woff

59 ms

PRmiXeptR36kaC0GEAetxuSd7Sk-1zCox9FpyOEBNq8.woff

PRmiXeptR36kaC0GEAetxuSd7Sk-1zCox9FpyOEBNq8.woff

57 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

34 ms

analytics.js

analytics.js

38 ms

MAPProc.aspx

MAPProc.aspx

293 ms

fbevents.js

fbevents.js

28 ms

collect

collect

16 ms

23 ms

collect

collect

60 ms

1pix.gif

1pix.gif

83 ms

Accessibility Review

obitsarchive.com accessibility score

84

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

Links do not have a discernible name

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

Best Practices

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

obitsarchive.com SEO score

96

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Obitsarchive.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Obitsarchive.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

obitsarchive.com

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