Tools & Wizards About Us
parting.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 62

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

parting.com

Compare Funeral Home Prices and Cremation Costs | Parting

Page Load Speed

3.2 sec in total

First Response

268 ms

Resources Loaded

2.6 sec

Page Rendered

321 ms

parting.com screenshot

About Website

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

Compare funeral home prices, see photos, and read reviews on Parting. Get help planning a traditional burial, direct cremation, or other funeral service.

Visit parting.com

Key Findings

We analyzed Parting.com page load time and found that the first response time was 268 ms and then it took 3 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

parting.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

31/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.0 s

13/100

10%

Network Requests Diagram

www.parting.com

268 ms

css

324 ms

10004122-10005251.js

761 ms

main.min.css

160 ms

js

434 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 43% of them (21 requests) were addressed to the original Parting.com, 12% (6 requests) were made to Maps.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (951 ms) relates to the external source D24n15hnbwhuhn.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 50.8 kB (7%)

Content Size

777.9 kB

After Optimization

727.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Parting.com main page is 777.9 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. 65% of websites need less resources to load. Images take 458.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 33.0 kB

  • Original 43.7 kB
  • After minification 43.6 kB
  • After compression 10.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. 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 33.0 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 16.6 kB

  • Original 458.4 kB
  • After minification 441.9 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. Parting images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.2 kB

  • Original 275.8 kB
  • After minification 275.8 kB
  • After compression 274.6 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.

Requests Breakdown

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

Requests Now

45

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.parting.com

www.parting.com

268 ms

css

css

324 ms

10004122-10005251.js

10004122-10005251.js

761 ms

main.min.css

main.min.css

160 ms

js

js

434 ms

vendor.min.js

vendor.min.js

319 ms

client.min.js

client.min.js

304 ms

conversion.js

conversion.js

428 ms

7937712370.js

7937712370.js

504 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

119 ms

amplitude-3.4.0-min.gz.js

amplitude-3.4.0-min.gz.js

951 ms

fbevents.js

fbevents.js

813 ms

parting-logo@2x.7a4b4c664cdc.png

parting-logo@2x.7a4b4c664cdc.png

767 ms

homepage-hero@2x.68083964b88f.jpg

homepage-hero@2x.68083964b88f.jpg

665 ms

new-york-times-logo.d08eb74a1be9.png

new-york-times-logo.d08eb74a1be9.png

619 ms

NBC_News_print_logo_2011.ace402ca6d49.png

NBC_News_print_logo_2011.ace402ca6d49.png

665 ms

forbes.1990bb2cea50.png

forbes.1990bb2cea50.png

675 ms

npr.c60721c67fd9.png

npr.c60721c67fd9.png

664 ms

cnbc-logo@2x.e4ac4a2e3ea3.png

cnbc-logo@2x.e4ac4a2e3ea3.png

665 ms

Huffington-Post-Logo.6614ae63b318.png

Huffington-Post-Logo.6614ae63b318.png

674 ms

aarp-logo@2x.8a9104450fd4.png

aarp-logo@2x.8a9104450fd4.png

781 ms

icon-stress_free_square@2x.967033bf22b6.png

icon-stress_free_square@2x.967033bf22b6.png

721 ms

icon-right_choice_square@2x.30354fbb46c3.png

icon-right_choice_square@2x.30354fbb46c3.png

721 ms

icon-save_time_square@2x.5abf9e8b085d.png

icon-save_time_square@2x.5abf9e8b085d.png

720 ms

homepage-process2@2x.748e4fd1cbf7.jpg

homepage-process2@2x.748e4fd1cbf7.jpg

779 ms

homepage-process1@2x.0a68224c413b.jpg

homepage-process1@2x.0a68224c413b.jpg

782 ms

homepage-process3@2x.c1db70827295.jpg

homepage-process3@2x.c1db70827295.jpg

816 ms

parting-logo-white@2x.e92ffb46004f.png

parting-logo-white@2x.e92ffb46004f.png

790 ms

a7937712370.html

a7937712370.html

370 ms

event

event

274 ms

fs.js

fs.js

320 ms

analytics.js

analytics.js

275 ms

gen_204

gen_204

115 ms

common.js

common.js

118 ms

util.js

util.js

136 ms

controls.js

controls.js

115 ms

places_impl.js

places_impl.js

117 ms

244 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

206 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

206 ms

483324035200969

483324035200969

178 ms

powered-by-google-on-white3.png

powered-by-google-on-white3.png

101 ms

autocomplete-icons.png

autocomplete-icons.png

91 ms

collect

collect

44 ms

88 ms

collect

collect

76 ms

7937712370.html

7937712370.html

228 ms

shim.latest.js

shim.latest.js

43 ms

roundtrip.js

roundtrip.js

22 ms

Accessibility Review

parting.com accessibility score

87

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

parting.com best practices score

62

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

parting.com 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

    EN

  • Encoding

    UTF-8

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

parting.com

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