Tools & Wizards About Us
edwardsvaham.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

edwardsvaham.com

Edwards Virginia Smokehouse | Authentic Smoked Meats Since 1926 | Edwards Virginia Smokehouse

Page Load Speed

1.2 sec in total

First Response

59 ms

Resources Loaded

1 sec

Page Rendered

146 ms

edwardsvaham.com screenshot

About Website

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

Welcome to Edwards Virginia Smokehouse! To us, a country ham is synonymous with family tradition. It's the flavor of dry-cured, hickory-smoked country ham that brings you to come back time and time ag...

Visit edwardsvaham.com

Key Findings

We analyzed Edwardsvaham.com page load time and found that the first response time was 59 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

edwardsvaham.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value2,510 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.045

99/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

edwardsvaham.com

59 ms

www.edwardsvaham.com

269 ms

93462b37ffb1047c79f2e3333284aa4a.css

8 ms

4bb4698e6262c0c1412cd70492d4ae42.css

41 ms

91cac5aaacca8b74b2d48ec270fc7a3f.css

35 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 65% of them (35 requests) were addressed to the original Edwardsvaham.com, 15% (8 requests) were made to Static.klaviyo.com and 15% (8 requests) were made to Js.klevu.com. The less responsive or slowest element that took the longest time to load (275 ms) relates to the external source Static.klaviyo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 235.7 kB (25%)

Content Size

942.7 kB

After Optimization

706.9 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Edwardsvaham.com main page is 942.7 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. 60% of websites need less resources to load. Javascripts take 499.3 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 232.8 kB

  • Original 275.4 kB
  • After minification 275.0 kB
  • After compression 42.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 232.8 kB or 85% of the original size.

JavaScript Optimization

-0%

Potential reduce by 215 B

  • Original 499.3 kB
  • After minification 499.3 kB
  • After compression 499.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

-2%

Potential reduce by 2.7 kB

  • Original 167.9 kB
  • After minification 167.9 kB
  • After compression 165.2 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. Edwardsvaham.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (61%)

Requests Now

33

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

edwardsvaham.com

edwardsvaham.com

59 ms

www.edwardsvaham.com

www.edwardsvaham.com

269 ms

93462b37ffb1047c79f2e3333284aa4a.css

93462b37ffb1047c79f2e3333284aa4a.css

8 ms

4bb4698e6262c0c1412cd70492d4ae42.css

4bb4698e6262c0c1412cd70492d4ae42.css

41 ms

91cac5aaacca8b74b2d48ec270fc7a3f.css

91cac5aaacca8b74b2d48ec270fc7a3f.css

35 ms

6a2b40880f92e52988323a025deb6688.js

6a2b40880f92e52988323a025deb6688.js

80 ms

klaviyo.js

klaviyo.js

275 ms

logo_3.png

logo_3.png

36 ms

EDW-V218-2023.jpg

EDW-V218-2023.jpg

78 ms

edwards-over95years-1.jpg

edwards-over95years-1.jpg

73 ms

logo-footer_1.png

logo-footer_1.png

78 ms

cc-footer.png

cc-footer.png

76 ms

Edwards-Top3-Bacon.jpg

Edwards-Top3-Bacon.jpg

38 ms

smokedhams.jpg

smokedhams.jpg

37 ms

carepackages-10.jpg

carepackages-10.jpg

40 ms

welcome-bgd.jpg

welcome-bgd.jpg

39 ms

social-icon.png

social-icon.png

39 ms

opensans-400.woff

opensans-400.woff

100 ms

opensans-400.woff

opensans-400.woff

120 ms

opensans-300.woff

opensans-300.woff

198 ms

opensans-300.woff

opensans-300.woff

137 ms

opensans-600.woff

opensans-600.woff

137 ms

opensans-600.woff

opensans-600.woff

199 ms

opensans-700.woff

opensans-700.woff

229 ms

opensans-700.woff

opensans-700.woff

228 ms

gtm.js

gtm.js

57 ms

klevu-webstore.js

klevu-webstore.js

44 ms

klevu-16589822964159537.js

klevu-16589822964159537.js

17 ms

porto-icons.woff

porto-icons.woff

26 ms

porto-icons.woff

porto-icons.woff

27 ms

franklingothic-book.otf

franklingothic-book.otf

27 ms

franklingothic-book.otf

franklingothic-book.otf

26 ms

Lato-Bold.woff

Lato-Bold.woff

106 ms

Lato-Bold.woff

Lato-Bold.woff

26 ms

Lato-Regular.woff

Lato-Regular.woff

106 ms

Lato-Regular.woff

Lato-Regular.woff

90 ms

Lato-Light.woff

Lato-Light.woff

61 ms

Lato-Light.woff

Lato-Light.woff

61 ms

fender_analytics.113876fdc67592e7cbfd.js

fender_analytics.113876fdc67592e7cbfd.js

107 ms

static.047f24ade89e4aff54a9.js

static.047f24ade89e4aff54a9.js

107 ms

runtime.f0e7d4bf2a07ba450c3d.js

runtime.f0e7d4bf2a07ba450c3d.js

40 ms

sharedUtils.e8c90ec039ff40fd1c44.js

sharedUtils.e8c90ec039ff40fd1c44.js

71 ms

vendors~signup_forms~post_identification_sync~web_personalization~reviews.79a680d9b10daef823dd.js

vendors~signup_forms~post_identification_sync~web_personalization~reviews.79a680d9b10daef823dd.js

70 ms

vendors~signup_forms~post_identification_sync~onsite-triggering.98adbd4f3c00592d4b9b.js

vendors~signup_forms~post_identification_sync~onsite-triggering.98adbd4f3c00592d4b9b.js

70 ms

vendors~signup_forms.87a8144324ad4ca548d7.js

vendors~signup_forms.87a8144324ad4ca548d7.js

103 ms

default~signup_forms~onsite-triggering.88e27c46b11194aaa904.js

default~signup_forms~onsite-triggering.88e27c46b11194aaa904.js

103 ms

signup_forms.53f6f8ccb52efe5fc472.js

signup_forms.53f6f8ccb52efe5fc472.js

102 ms

klevu-16589822964159537-maps.js

klevu-16589822964159537-maps.js

41 ms

klevu-16589822964159537-banner.js

klevu-16589822964159537-banner.js

60 ms

klevu_search_box_klevu-16589822964159537.min.css

klevu_search_box_klevu-16589822964159537.min.css

255 ms

klevu-layout-slim.js

klevu-layout-slim.js

61 ms

ab22e369c4d25e6994758dbd002489c1.css

ab22e369c4d25e6994758dbd002489c1.css

17 ms

klevu-loader.GIF

klevu-loader.GIF

13 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

20 ms

Accessibility Review

edwardsvaham.com accessibility score

84

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

[role]s do not have all required [aria-*] attributes

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.

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

edwardsvaham.com best practices score

67

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

edwardsvaham.com SEO score

85

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

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

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

edwardsvaham.com

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