Tools & Wizards About Us
williamsburgpetloss.com screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

williamsburgpetloss.com

Williamsburg Pet Loss - compassionate, private, local pet cremation.

Page Load Speed

3.4 sec in total

First Response

365 ms

Resources Loaded

2.8 sec

Page Rendered

233 ms

williamsburgpetloss.com screenshot

About Website

Click here to check amazing Williamsburg Pet Loss content. Otherwise, check out these important facts you probably never knew about williamsburgpetloss.com

Williamsburg Pet Loss is the only local business to offer compassionate “private” pet cremation services utilizing technology to ensure that the cremains delivered are those of the owner's pet.

Visit williamsburgpetloss.com

Key Findings

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

williamsburgpetloss.com performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value3.8 s

83/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value7.4 s

48/100

10%

Network Requests Diagram

williamsburgpetloss.com

365 ms

style_screen.css

8 ms

wasocial.js

7 ms

style_dialogs.css

7 ms

style_forms.css

6 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 59% of them (41 requests) were addressed to the original Williamsburgpetloss.com, 12% (8 requests) were made to Static.xx.fbcdn.net and 9% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.7 kB (10%)

Content Size

980.9 kB

After Optimization

883.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-72%

Potential reduce by 19.6 kB

  • Original 27.2 kB
  • After minification 25.6 kB
  • After compression 7.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 19.6 kB or 72% of the original size.

Image Optimization

-3%

Potential reduce by 22.9 kB

  • Original 690.9 kB
  • After minification 668.0 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. Williamsburg Pet Loss images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 51.9 kB

  • Original 254.4 kB
  • After minification 254.3 kB
  • After compression 202.4 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 51.9 kB or 20% of the original size.

CSS Optimization

-39%

Potential reduce by 3.3 kB

  • Original 8.3 kB
  • After minification 7.3 kB
  • After compression 5.1 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. Williamsburgpetloss.com needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 39% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (48%)

Requests Now

66

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

williamsburgpetloss.com

williamsburgpetloss.com

365 ms

style_screen.css

style_screen.css

8 ms

wasocial.js

wasocial.js

7 ms

style_dialogs.css

style_dialogs.css

7 ms

style_forms.css

style_forms.css

6 ms

wasocial.css

wasocial.css

6 ms

shadowbox.css

shadowbox.css

7 ms

shadowbox.js

shadowbox.js

12 ms

SprySlidingPanels.js

SprySlidingPanels.js

25 ms

SprySlidingPanels.css

SprySlidingPanels.css

29 ms

jquery.js

jquery.js

21 ms

jquery.innerfade.js

jquery.innerfade.js

20 ms

ga.js

ga.js

83 ms

plusone.js

plusone.js

101 ms

widgets.js

widgets.js

120 ms

btn_paynowCC_LG.gif

btn_paynowCC_LG.gif

124 ms

bkg_page.jpg

bkg_page.jpg

25 ms

bkg_semi-transparent.png

bkg_semi-transparent.png

26 ms

facebook.png

facebook.png

25 ms

twitter.png

twitter.png

25 ms

mail.png

mail.png

25 ms

logo_wpl.png

logo_wpl.png

25 ms

bkg_nav.png

bkg_nav.png

41 ms

brochures_collage_wpl.jpg

brochures_collage_wpl.jpg

41 ms

Capture.JPG

Capture.JPG

41 ms

Capture2.JPG

Capture2.JPG

46 ms

Notes%20for%20webpage%202.jpg

Notes%20for%20webpage%202.jpg

42 ms

Notes%20for%20webpage%204.jpg

Notes%20for%20webpage%204.jpg

46 ms

Notes%20for%20webpage%203.jpg

Notes%20for%20webpage%203.jpg

45 ms

arrow_button_129x24.png

arrow_button_129x24.png

45 ms

billboard1.jpg

billboard1.jpg

93 ms

billboard2.jpg

billboard2.jpg

89 ms

billboard3.jpg

billboard3.jpg

88 ms

billboard4.jpg

billboard4.jpg

90 ms

why_photo.jpg

why_photo.jpg

84 ms

benefits_photo.jpg

benefits_photo.jpg

62 ms

pdf.png

pdf.png

88 ms

bullet_circle_arrow.png

bullet_circle_arrow.png

86 ms

bkg_help_now.gif

bkg_help_now.gif

88 ms

bkg_footer_top.jpg

bkg_footer_top.jpg

91 ms

paw_facebook.png

paw_facebook.png

89 ms

paw_twitter.png

paw_twitter.png

89 ms

paw_google.png

paw_google.png

89 ms

ascpa_logo.png

ascpa_logo.png

89 ms

__utm.gif

__utm.gif

26 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

33 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

53 ms

fastbutton

fastbutton

51 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

161 ms

postmessageRelay

postmessageRelay

60 ms

style_print.css

style_print.css

9 ms

developers.google.com

developers.google.com

327 ms

3588414169-postmessagerelay.js

3588414169-postmessagerelay.js

25 ms

rpc:shindig_random.js

rpc:shindig_random.js

5 ms

likebox.php

likebox.php

659 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

settings

settings

99 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

22 ms

embeds

embeds

40 ms

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

36 ms

w-Kbjwch27U.css

w-Kbjwch27U.css

524 ms

sGcGGNWA3Bv.js

sGcGGNWA3Bv.js

1004 ms

teTZ2tZqwkq.js

teTZ2tZqwkq.js

847 ms

BECqV_OB-Tv.js

BECqV_OB-Tv.js

1051 ms

xNa_5SPtPNu.js

xNa_5SPtPNu.js

1034 ms

q4SZVAjzsaO.js

q4SZVAjzsaO.js

1045 ms

p55HfXW__mM.js

p55HfXW__mM.js

900 ms

300523321_364340659242453_134588279943310602_n.jpg

300523321_364340659242453_134588279943310602_n.jpg

460 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

128 ms

Accessibility Review

williamsburgpetloss.com accessibility score

65

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

<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

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

williamsburgpetloss.com best practices score

58

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

Browser errors were logged to the console

SEO Factors

williamsburgpetloss.com SEO score

50

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

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

williamsburgpetloss.com

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