Tools & Wizards About Us
vanorsdel.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

vanorsdel.com

Van Orsdel Funeral & Cremation Services - Funeral Homes Miami FL Cremation

Page Load Speed

3.2 sec in total

First Response

253 ms

Resources Loaded

2.3 sec

Page Rendered

645 ms

vanorsdel.com screenshot

About Website

Click here to check amazing Van Orsdel content. Otherwise, check out these important facts you probably never knew about vanorsdel.com

Funeral Homes Miami, Florida. Cremation Services Miami, Florida. Miami Beach, Midtown Miami, Coral Gables, Florida. Cremation Services.

Visit vanorsdel.com

Key Findings

We analyzed Vanorsdel.com page load time and found that the first response time was 253 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

vanorsdel.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value2,420 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value24.4 s

0/100

10%

Network Requests Diagram

vanorsdel.com

253 ms

www.vanorsdel.com

320 ms

gtm.js

95 ms

gtm.js

185 ms

vendor.min.css

35 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Vanorsdel.com, 22% (17 requests) were made to Cdn.f1connect.net and 21% (16 requests) were made to 30secondfeedback.com. The less responsive or slowest element that took the longest time to load (537 ms) relates to the external source 30secondfeedback.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 67.8 kB (13%)

Content Size

520.4 kB

After Optimization

452.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vanorsdel.com main page is 520.4 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. Only a small number of websites need less resources to load. Javascripts take 229.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 53.0 kB

  • Original 67.7 kB
  • After minification 67.2 kB
  • After compression 14.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 53.0 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 1.9 kB

  • Original 206.2 kB
  • After minification 204.3 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. Van Orsdel images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 9.7 kB

  • Original 229.8 kB
  • After minification 229.6 kB
  • After compression 220.1 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

-19%

Potential reduce by 3.1 kB

  • Original 16.7 kB
  • After minification 16.7 kB
  • After compression 13.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. Vanorsdel.com needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (75%)

Requests Now

56

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vanorsdel.com

vanorsdel.com

253 ms

www.vanorsdel.com

www.vanorsdel.com

320 ms

gtm.js

gtm.js

95 ms

gtm.js

gtm.js

185 ms

vendor.min.css

vendor.min.css

35 ms

theme.min.css

theme.min.css

51 ms

skin.css

skin.css

153 ms

custom.css

custom.css

77 ms

js

js

218 ms

widgets.js

widgets.js

537 ms

theme.min.js

theme.min.js

80 ms

custom.js

custom.js

177 ms

widget.js

widget.js

271 ms

js

js

135 ms

js

js

133 ms

gtm.js

gtm.js

115 ms

beacon

beacon

509 ms

logo.63839880835_fc_white.png

logo.63839880835_fc_white.png

154 ms

ScreenShot2021-01-04at6.27.03PM.png

ScreenShot2021-01-04at6.27.03PM.png

155 ms

Poppins-Light.woff

Poppins-Light.woff

39 ms

js

js

88 ms

Poppins-Black.woff

Poppins-Black.woff

234 ms

Poppins-Medium.woff

Poppins-Medium.woff

234 ms

PlayfairDisplay-Medium.woff

PlayfairDisplay-Medium.woff

232 ms

Poppins-SemiBold.woff

Poppins-SemiBold.woff

234 ms

PlayfairDisplay-Regular.woff

PlayfairDisplay-Regular.woff

231 ms

Poppins-Bold.woff

Poppins-Bold.woff

352 ms

ionicons.woff

ionicons.woff

296 ms

281 ms

js

js

160 ms

analytics.js

analytics.js

223 ms

vanorsdelfuneralcremationservicesmulti

vanorsdelfuneralcremationservicesmulti

253 ms

loader.gif

loader.gif

298 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

154 ms

loader.js

loader.js

151 ms

loader.js

loader.js

205 ms

collect

collect

57 ms

css2

css2

84 ms

stream.css

stream.css

89 ms

review-tool-style.css

review-tool-style.css

154 ms

all.min.js

all.min.js

91 ms

css2

css2

99 ms

jquery.min.js

jquery.min.js

90 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

187 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

216 ms

jquery.popover.css

jquery.popover.css

226 ms

jquery.min.js

jquery.min.js

429 ms

popper.min.js

popper.min.js

101 ms

bootstrap.min.js

bootstrap.min.js

241 ms

flexslider.css

flexslider.css

227 ms

jquery.min.js

jquery.min.js

96 ms

jquery.flexslider.js

jquery.flexslider.js

265 ms

stream.js

stream.js

280 ms

widget_app_base_1709553975535.js

widget_app_base_1709553975535.js

51 ms

55 ms

call-tracking_7.js

call-tracking_7.js

13 ms

app.js

app.js

23 ms

wcm

wcm

13 ms

4860-283-10-9151.js

4860-283-10-9151.js

38 ms

c

c

49 ms

application2.js

application2.js

88 ms

google-social-share.png

google-social-share.png

133 ms

left-quote.png

left-quote.png

135 ms

right-quote.png

right-quote.png

159 ms

storage.html

storage.html

29 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMPrQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMPrQ.ttf

54 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4bbLPrQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4bbLPrQ.ttf

131 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LPrQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LPrQ.ttf

137 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejLPrQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejLPrQ.ttf

140 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4cHLPrQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4cHLPrQ.ttf

140 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

139 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf

138 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf

137 ms

storage.js

storage.js

101 ms

q771cdwc

q771cdwc

105 ms

have-questions.png

have-questions.png

43 ms

Accessibility Review

vanorsdel.com accessibility score

94

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-hidden="true"] elements contain focusable descendents

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

Links do not have a discernible name

Best Practices

vanorsdel.com best practices score

75

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

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

vanorsdel.com SEO score

93

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

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

vanorsdel.com

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