Tools & Wizards About Us
stonfield.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

stonfield.com

ClickFunnels™ - Marketing Funnels and Landing Pages that Convert

Page Load Speed

2.6 sec in total

First Response

664 ms

Resources Loaded

1.7 sec

Page Rendered

163 ms

stonfield.com screenshot

About Website

Click here to check amazing Stonfield content. Otherwise, check out these important facts you probably never knew about stonfield.com

ClickFunnels™ - Marketing Funnels and Landing Pages that Convert

Visit stonfield.com

Key Findings

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

stonfield.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

65/100

25%

SI (Speed Index)

Value3.1 s

92/100

10%

TBT (Total Blocking Time)

Value2,290 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

stonfield.com

664 ms

wp-emoji-release.min.js

141 ms

style.css

188 ms

skeleton.css

116 ms

responsive.css

164 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 98% of them (65 requests) were addressed to the original Stonfield.com, 2% (1 request) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (664 ms) belongs to the original domain Stonfield.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 606.5 kB (48%)

Content Size

1.3 MB

After Optimization

644.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 35.3 kB

  • Original 44.8 kB
  • After minification 43.2 kB
  • After compression 9.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 35.3 kB or 79% of the original size.

Image Optimization

-20%

Potential reduce by 134.4 kB

  • Original 666.3 kB
  • After minification 531.9 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. Obviously, Stonfield needs image optimization as it can save up to 134.4 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 159.8 kB

  • Original 222.9 kB
  • After minification 217.2 kB
  • After compression 63.2 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 159.8 kB or 72% of the original size.

CSS Optimization

-87%

Potential reduce by 277.0 kB

  • Original 316.9 kB
  • After minification 233.0 kB
  • After compression 39.8 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. Stonfield.com needs all CSS files to be minified and compressed as it can save up to 277.0 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

63

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stonfield.com

stonfield.com

664 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

141 ms

style.css

style.css

188 ms

skeleton.css

skeleton.css

116 ms

responsive.css

responsive.css

164 ms

ceceppaml.css

ceceppaml.css

132 ms

styles.css

styles.css

133 ms

flexslider.css

flexslider.css

141 ms

style.css

style.css

652 ms

juiz_last_tweet.css

juiz_last_tweet.css

168 ms

tp_twitter_plugin.css

tp_twitter_plugin.css

164 ms

settings.css

settings.css

192 ms

captions.css

captions.css

197 ms

styles.css

styles.css

194 ms

magnific-popup.css

magnific-popup.css

202 ms

jquery.js

jquery.js

236 ms

jquery-migrate.min.js

jquery-migrate.min.js

216 ms

ceceppaml.js

ceceppaml.js

217 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

231 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

302 ms

easing.js

easing.js

243 ms

fitvids.js

fitvids.js

244 ms

js

js

20 ms

basic.css

basic.css

85 ms

headers.css

headers.css

82 ms

bootstrap.css

bootstrap.css

89 ms

shortcodes.css

shortcodes.css

136 ms

flexslider.css

flexslider.css

108 ms

prettyPhoto.css

prettyPhoto.css

120 ms

twitter.png

twitter.png

116 ms

facebook.png

facebook.png

119 ms

skype.png

skype.png

120 ms

google.png

google.png

116 ms

linkedin.png

linkedin.png

117 ms

youtube.png

youtube.png

119 ms

mystonfield-1502.png

mystonfield-1502.png

119 ms

slide2.jpg

slide2.jpg

122 ms

sl23.png

sl23.png

123 ms

Fotolia_53885822_S.jpg

Fotolia_53885822_S.jpg

167 ms

sl3t11.png

sl3t11.png

119 ms

sl3t21.png

sl3t21.png

120 ms

boutique.png

boutique.png

122 ms

Fotolia_53159416_S.jpg

Fotolia_53159416_S.jpg

204 ms

Fotolia_54130852_S2.jpg

Fotolia_54130852_S2.jpg

239 ms

WBT.png

WBT.png

136 ms

kcp1.jpg

kcp1.jpg

136 ms

ucb1.jpg

ucb1.jpg

124 ms

covidien1.jpg

covidien1.jpg

136 ms

philips1.jpg

philips1.jpg

159 ms

securitas1.jpg

securitas1.jpg

159 ms

hp.jpg

hp.jpg

161 ms

ca1.jpg

ca1.jpg

185 ms

stago1.jpg

stago1.jpg

186 ms

gdf1.jpg

gdf1.jpg

188 ms

astute1.jpg

astute1.jpg

199 ms

alere.jpg

alere.jpg

215 ms

ace.jpg

ace.jpg

212 ms

search.png

search.png

206 ms

timer.png

timer.png

223 ms

stripes.png

stripes.png

181 ms

loader.gif

loader.gif

183 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

171 ms

coloredbg.png

coloredbg.png

31 ms

slider-prev.png

slider-prev.png

38 ms

slider-next.png

slider-next.png

37 ms

retina.css

retina.css

30 ms

Accessibility Review

stonfield.com accessibility score

82

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

SEO Factors

stonfield.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 Stonfield.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 Stonfield.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

stonfield.com

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