Tools & Wizards About Us
indywilbert.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

indywilbert.com

Wilbert Vault | Burial Vaults | Indianapolis, IN | Urns

Page Load Speed

932 ms in total

First Response

56 ms

Resources Loaded

792 ms

Page Rendered

84 ms

indywilbert.com screenshot

About Website

Welcome to indywilbert.com homepage info - get ready to check Indy Wilbert best content right away, or after learning these important things about indywilbert.com

Wilbert Burial Vault of Indianapolis, IN provides burial services and burial products to 14 counties in Indiana. Products include burial vaults and cremation urns, as well as keepsakes, burial vault m...

Visit indywilbert.com

Key Findings

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

indywilbert.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

60/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value3,010 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.263

47/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

indywilbert.com

56 ms

www.indywilbert.com

31 ms

www.indywilbert.com

133 ms

design.css

95 ms

css

32 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 29% of them (9 requests) were addressed to the original Indywilbert.com, 32% (10 requests) were made to Wilbertcore.com and 16% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (143 ms) relates to the external source Youtube.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 22.4 kB (6%)

Content Size

402.6 kB

After Optimization

380.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Indywilbert.com main page is 402.6 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. 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. Javascripts take 168.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 13.9 kB

  • Original 19.3 kB
  • After minification 19.1 kB
  • After compression 5.4 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 13.9 kB or 72% of the original size.

Image Optimization

-3%

Potential reduce by 3.7 kB

  • Original 143.1 kB
  • After minification 139.4 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. Indy Wilbert images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.7 kB

  • Original 168.5 kB
  • After minification 168.5 kB
  • After compression 165.8 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

-3%

Potential reduce by 2.1 kB

  • Original 71.6 kB
  • After minification 71.6 kB
  • After compression 69.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. Indywilbert.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (44%)

Requests Now

27

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

indywilbert.com

indywilbert.com

56 ms

www.indywilbert.com

www.indywilbert.com

31 ms

www.indywilbert.com

www.indywilbert.com

133 ms

design.css

design.css

95 ms

css

css

32 ms

jquery.js

jquery.js

56 ms

colorbox.css

colorbox.css

55 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

55 ms

functions.js

functions.js

107 ms

all.js

all.js

41 ms

location.gif

location.gif

68 ms

gZCWlRHoQnE

gZCWlRHoQnE

143 ms

loading.gif

loading.gif

67 ms

controls.png

controls.png

66 ms

logo-wilbert_burial_vault.gif

logo-wilbert_burial_vault.gif

54 ms

submit_order.gif

submit_order.gif

58 ms

alive_and_well.png

alive_and_well.png

55 ms

Burial_Vault_Cremation_Urn_lady_with_flowers_sun.jpg

Burial_Vault_Cremation_Urn_lady_with_flowers_sun.jpg

68 ms

pattern-banner_text_bar.png

pattern-banner_text_bar.png

58 ms

banner_w.png

banner_w.png

56 ms

beige.jpg

beige.jpg

83 ms

personalization_vault-american_flag.png

personalization_vault-american_flag.png

101 ms

font

font

141 ms

all.js

all.js

8 ms

www-player.css

www-player.css

6 ms

www-embed-player.js

www-embed-player.js

24 ms

base.js

base.js

48 ms

ad_status.js

ad_status.js

129 ms

V6n6N6lR58V6YvKWzRgNRm2UbnEaYiTpGDY0zZzDx9c.js

V6n6N6lR58V6YvKWzRgNRm2UbnEaYiTpGDY0zZzDx9c.js

82 ms

embed.js

embed.js

24 ms

id

id

23 ms

Accessibility Review

indywilbert.com accessibility score

88

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.

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

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

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

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

    N/A

  • Encoding

    UTF-8

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

indywilbert.com

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