Tools & Wizards About Us
peseski.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

peseski.com

Home | Hinnegan-Peseski Funeral Home located in Chatham, ON

Page Load Speed

964 ms in total

First Response

26 ms

Resources Loaded

485 ms

Page Rendered

453 ms

peseski.com screenshot

About Website

Click here to check amazing Peseski content for Canada. Otherwise, check out these important facts you probably never knew about peseski.com

At Hinnegan-Peseski we are pleased to have maintained our firm as a family owned and operated business for over a 110 years.

Visit peseski.com

Key Findings

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

peseski.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value13.2 s

0/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value2,170 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

peseski.com

26 ms

gtm.js

113 ms

optimize.js

59 ms

css

41 ms

css

57 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 86% of them (57 requests) were addressed to the original Peseski.com, 6% (4 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (113 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 35.8 kB (55%)

Content Size

64.5 kB

After Optimization

28.7 kB

  • HTML
  • JavaScript

In fact, the total size of Peseski.com main page is 64.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. 80% 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. HTML takes 43.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 35.7 kB

  • Original 43.5 kB
  • After minification 31.3 kB
  • After compression 7.8 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 12.2 kB, which is 28% 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 35.7 kB or 82% of the original size.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.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.

Requests Breakdown

Number of requests can be reduced by 26 (41%)

Requests Now

63

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

peseski.com

peseski.com

26 ms

gtm.js

gtm.js

113 ms

optimize.js

optimize.js

59 ms

css

css

41 ms

css

css

57 ms

css

css

75 ms

css

css

75 ms

standard-styles.css

standard-styles.css

9 ms

normalize.min.css

normalize.min.css

18 ms

layout-styles.css

layout-styles.css

21 ms

skin.css

skin.css

22 ms

responsive.css

responsive.css

20 ms

brown-red.css

brown-red.css

20 ms

colorscheme-color-3.css

colorscheme-color-3.css

22 ms

yui-min.js

yui-min.js

23 ms

YuiConfig.js

YuiConfig.js

27 ms

respond.min.js

respond.min.js

23 ms

SiteAnnouncementRenderController.js

SiteAnnouncementRenderController.js

24 ms

GoogleTagManagerClickHandler.js

GoogleTagManagerClickHandler.js

24 ms

combo.html

combo.html

19 ms

analytics.js

analytics.js

99 ms

main_bg_gen3.jpg

main_bg_gen3.jpg

81 ms

obit-bg_gen3.png

obit-bg_gen3.png

75 ms

nav-icon.png

nav-icon.png

14 ms

logo.jpg

logo.jpg

13 ms

pattern_gen3.png

pattern_gen3.png

13 ms

slide-shadow.png

slide-shadow.png

14 ms

FuneralHome2017.jpg

FuneralHome2017.jpg

77 ms

Funeral_Home_1890s.png

Funeral_Home_1890s.png

75 ms

Funeral_Home_1940s.png

Funeral_Home_1940s.png

78 ms

106533418.jpg

106533418.jpg

88 ms

slide5.jpg

slide5.jpg

75 ms

golden-frame.png

golden-frame.png

76 ms

main-bg.png

main-bg.png

83 ms

Ask-Director2.jpg

Ask-Director2.jpg

76 ms

gold-border.png

gold-border.png

80 ms

obit-bg.jpg

obit-bg.jpg

84 ms

Shelley-Lauzon.jpg

Shelley-Lauzon.jpg

85 ms

Della-Turner.jpg

Della-Turner.jpg

84 ms

Maria-Magliaro.jpeg

Maria-Magliaro.jpeg

81 ms

Sheila-Ross.jpg

Sheila-Ross.jpg

83 ms

Christine-Thompson.jpg

Christine-Thompson.jpg

86 ms

Wesley-Hooker.jpg

Wesley-Hooker.jpg

85 ms

Fernand-Gagnon.jpg

Fernand-Gagnon.jpg

87 ms

Debbie-Cottel.jpg

Debbie-Cottel.jpg

88 ms

Rita-Loretta-King.jpg

Rita-Loretta-King.jpg

88 ms

Bruce-Somerville.png

Bruce-Somerville.png

89 ms

Contact_-_Copy.jpg

Contact_-_Copy.jpg

89 ms

Immediate-Need.jpg

Immediate-Need.jpg

90 ms

Pre-PlanningNew.jpg

Pre-PlanningNew.jpg

90 ms

footer_gen3.png

footer_gen3.png

91 ms

bullet.png

bullet.png

91 ms

combo.html

combo.html

88 ms

javascript-combo.html

javascript-combo.html

85 ms

collect

collect

52 ms

merriweather-regular-webfont.woff

merriweather-regular-webfont.woff

27 ms

belgrano-regular-webfont.woff

belgrano-regular-webfont.woff

27 ms

combo.html

combo.html

12 ms

js

js

40 ms

facebook_32.png

facebook_32.png

17 ms

twitter_32.png

twitter_32.png

17 ms

linkedin_32.png

linkedin_32.png

17 ms

javascript-combo.html

javascript-combo.html

3 ms

combo.html

combo.html

18 ms

combo.html

combo.html

19 ms

combo.html

combo.html

19 ms

Accessibility Review

peseski.com accessibility score

64

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

peseski.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

peseski.com SEO score

78

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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

peseski.com

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