Tools & Wizards About Us
aspenfence.net screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

aspenfence.net

Residential and Commercial Fence Contractor | Aspen Fence Company

Page Load Speed

2.2 sec in total

First Response

137 ms

Resources Loaded

1.8 sec

Page Rendered

264 ms

aspenfence.net screenshot

About Website

Welcome to aspenfence.net homepage info - get ready to check Aspen Fence best content right away, or after learning these important things about aspenfence.net

Aspen Fence Company is a premiere residential and commercial fence contractor specializing in installing, replacing, and repairing all types of fences in the no

Visit aspenfence.net

Key Findings

We analyzed Aspenfence.net page load time and found that the first response time was 137 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

aspenfence.net performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

16/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value270 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value6.5 s

58/100

10%

Network Requests Diagram

aspenfence.net

137 ms

www.aspenfence.net

90 ms

bt

82 ms

require.min.js

54 ms

main-r.min.js

60 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Aspenfence.net, 53% (34 requests) were made to Static.parastorage.com and 22% (14 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (450 ms) relates to the external source Static.parastorage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (64%)

Content Size

3.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aspenfence.net main page is 3.5 MB. 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 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 91.8 kB

  • Original 109.9 kB
  • After minification 109.7 kB
  • After compression 18.2 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 91.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 489 B

  • Original 603.5 kB
  • After minification 603.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. Aspen Fence images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 2.1 MB

  • Original 2.8 MB
  • After minification 2.7 MB
  • After compression 639.6 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 2.1 MB or 77% of the original size.

CSS Optimization

-84%

Potential reduce by 44.1 kB

  • Original 52.5 kB
  • After minification 49.5 kB
  • After compression 8.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. Aspenfence.net needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

57

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aspenfence.net

aspenfence.net

137 ms

www.aspenfence.net

www.aspenfence.net

90 ms

bt

bt

82 ms

require.min.js

require.min.js

54 ms

main-r.min.js

main-r.min.js

60 ms

viewer.css

viewer.css

59 ms

dynamicmodel

dynamicmodel

46 ms

6f3501_a4d9565d79b649a9abefad80339a2e96_47.json.z

6f3501_a4d9565d79b649a9abefad80339a2e96_47.json.z

411 ms

6f3501_6ed81ca1ed9a1530832db0e67c168b8b_47.json.z

6f3501_6ed81ca1ed9a1530832db0e67c168b8b_47.json.z

413 ms

ugc-viewer

ugc-viewer

41 ms

bt

bt

156 ms

skins.min.js

skins.min.js

450 ms

components.min.js

components.min.js

57 ms

utils.min.js

utils.min.js

150 ms

core.min.js

core.min.js

104 ms

react-with-addons.min.js

react-with-addons.min.js

149 ms

lodash.min.js

lodash.min.js

41 ms

TweenMax.min.js

TweenMax.min.js

145 ms

layout.min.js

layout.min.js

101 ms

tpa.min.js

tpa.min.js

148 ms

fonts.min.js

fonts.min.js

142 ms

animations.min.js

animations.min.js

143 ms

swfobject.min.js

swfobject.min.js

143 ms

mousetrap.min.js

mousetrap.min.js

147 ms

tweenEngine.min.js

tweenEngine.min.js

143 ms

DrawSVGPlugin.min.js

DrawSVGPlugin.min.js

139 ms

react-dom.min.js

react-dom.min.js

135 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

135 ms

widgets.min.js

widgets.min.js

129 ms

experiment.js

experiment.js

133 ms

render.min.js

render.min.js

134 ms

wixappsCore.min.js

wixappsCore.min.js

135 ms

wixappsClassics.min.js

wixappsClassics.min.js

366 ms

wixappsBuilder.min.js

wixappsBuilder.min.js

131 ms

zepto.min.js

zepto.min.js

130 ms

color.min.js

color.min.js

133 ms

react-dom-server.min.js

react-dom-server.min.js

63 ms

bt

bt

72 ms

dc.js

dc.js

178 ms

bt

bt

421 ms

latin.css

latin.css

425 ms

6f3501_3b370fe747a9f4733853803a6b36d991.jpg

6f3501_3b370fe747a9f4733853803a6b36d991.jpg

373 ms

css

css

202 ms

__utm.gif

__utm.gif

135 ms

214ec6_fcfebc963286ee336cb7cf450b5cbb12.png

214ec6_fcfebc963286ee336cb7cf450b5cbb12.png

52 ms

214ec6_6fa282c45f35b9bdaf61145b7adb9352.png

214ec6_6fa282c45f35b9bdaf61145b7adb9352.png

68 ms

214ec6_33faa9ff990e88ae54d6fccbb14e1c5f.png

214ec6_33faa9ff990e88ae54d6fccbb14e1c5f.png

70 ms

6f3501_b96e4520218e8d8cb7526a3e7169f887.jpg

6f3501_b96e4520218e8d8cb7526a3e7169f887.jpg

306 ms

6f3501_feee0e860642ac5a5c75a6944dcbe6f5.jpg

6f3501_feee0e860642ac5a5c75a6944dcbe6f5.jpg

304 ms

6f3501_4305689da4a1ca3a2ef34703b5bed2b8.jpg

6f3501_4305689da4a1ca3a2ef34703b5bed2b8.jpg

292 ms

6f3501_27602bf857d0a75e317a84d6cedcaf93.jpg

6f3501_27602bf857d0a75e317a84d6cedcaf93.jpg

307 ms

6f3501_ed3cf9d6d087b91854e303138d9d5e1c.jpg

6f3501_ed3cf9d6d087b91854e303138d9d5e1c.jpg

254 ms

a9c60d982133f637be94bd5a5ce468a5.wix_mp

a9c60d982133f637be94bd5a5ce468a5.wix_mp

133 ms

6f3501_3b370fe747a9f4733853803a6b36d991.jpg

6f3501_3b370fe747a9f4733853803a6b36d991.jpg

412 ms

bt

bt

120 ms

bt

bt

119 ms

bt

bt

122 ms

bevel_300.png

bevel_300.png

73 ms

liftedshadow_medium.png

liftedshadow_medium.png

74 ms

apple_box.png

apple_box.png

74 ms

arrows_white_new3.png

arrows_white_new3.png

72 ms

5t8vP9Hx2udzw372glmOxA.ttf

5t8vP9Hx2udzw372glmOxA.ttf

18 ms

ugc-viewer

ugc-viewer

37 ms

a9c60d982133f637be94bd5a5ce468a5.wix_mp

a9c60d982133f637be94bd5a5ce468a5.wix_mp

4 ms

Accessibility Review

aspenfence.net accessibility score

78

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

button, link, and menuitem elements do not have accessible names.

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

aspenfence.net 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

High

Page has valid source maps

SEO Factors

aspenfence.net SEO score

83

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

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

    N/A

  • Encoding

    UTF-8

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

aspenfence.net

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