Tools & Wizards About Us
lannonstone.net screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    35% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

lannonstone.net

Lannon Stone - Home

Page Load Speed

4.9 sec in total

First Response

292 ms

Resources Loaded

2.7 sec

Page Rendered

1.9 sec

lannonstone.net screenshot

About Website

Visit lannonstone.net now to see the best up-to-date Lannon Stone content and also check out these interesting facts you probably never knew about lannonstone.net

We produce and sell quality construction aggregates, limestone, stone, sand, and gravel from 6 locations in Southeast Wisconsin, serving the concrete, asphalt, road-building, grading, utility, landsca...

Visit lannonstone.net

Key Findings

We analyzed Lannonstone.net page load time and found that the first response time was 292 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

lannonstone.net performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value16.3 s

0/100

10%

TBT (Total Blocking Time)

Value2,090 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value21.0 s

1/100

10%

Network Requests Diagram

lannonstone.net

292 ms

css

50 ms

duplicate-page-and-post-admin.min.css

124 ms

style-frontend.css

125 ms

qode-quick-links.min.css

137 ms

Our browser made a total of 138 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Lannonstone.net, 78% (108 requests) were made to 2tzp833qdco01g48l7whle81.wpengine.netdna-cdn.com and 7% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Lannonstone.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (53%)

Content Size

3.9 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lannonstone.net main page is 3.9 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. 85% 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. CSS take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 75.2 kB

  • Original 87.4 kB
  • After minification 85.6 kB
  • After compression 12.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 75.2 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 124 B

  • Original 1.4 MB
  • After minification 1.4 MB

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. Lannon Stone images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 481.2 kB

  • Original 718.8 kB
  • After minification 710.9 kB
  • After compression 237.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 481.2 kB or 67% of the original size.

CSS Optimization

-87%

Potential reduce by 1.5 MB

  • Original 1.7 MB
  • After minification 1.6 MB
  • After compression 213.7 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. Lannonstone.net needs all CSS files to be minified and compressed as it can save up to 1.5 MB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 105 (85%)

Requests Now

123

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lannonstone.net

lannonstone.net

292 ms

css

css

50 ms

duplicate-page-and-post-admin.min.css

duplicate-page-and-post-admin.min.css

124 ms

style-frontend.css

style-frontend.css

125 ms

qode-quick-links.min.css

qode-quick-links.min.css

137 ms

settings.css

settings.css

129 ms

superfish.css

superfish.css

126 ms

style.css

style.css

127 ms

event_template.css

event_template.css

137 ms

responsive.css

responsive.css

132 ms

css

css

115 ms

style.css

style.css

132 ms

font-awesome.min.css

font-awesome.min.css

130 ms

style.min.css

style.min.css

137 ms

style.css

style.css

140 ms

dripicons.css

dripicons.css

133 ms

stylesheet.min.css

stylesheet.min.css

225 ms

print.css

print.css

138 ms

timetable-schedule.min.css

timetable-schedule.min.css

137 ms

timetable-schedule-responsive.min.css

timetable-schedule-responsive.min.css

141 ms

style_dynamic.css

style_dynamic.css

137 ms

responsive.min.css

responsive.min.css

143 ms

style_dynamic_responsive.css

style_dynamic_responsive.css

141 ms

vertical_responsive.min.css

vertical_responsive.min.css

149 ms

js_composer.min.css

js_composer.min.css

162 ms

custom_css.css

custom_css.css

151 ms

jquery.js

jquery.js

305 ms

jquery-migrate.min.js

jquery-migrate.min.js

197 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

212 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

195 ms

ihk5nwh.js

ihk5nwh.js

310 ms

style.css

style.css

300 ms

default.min.js

default.min.js

295 ms

plugins.js

plugins.js

298 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

295 ms

jquery.mCustomScrollbar.min.js

jquery.mCustomScrollbar.min.js

294 ms

qode-quick-links.min.js

qode-quick-links.min.js

294 ms

core.min.js

core.min.js

293 ms

widget.min.js

widget.min.js

317 ms

tabs.min.js

tabs.min.js

301 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

108 ms

jquery.ba-bbq.min.js

jquery.ba-bbq.min.js

234 ms

jquery.carouFredSel-6.2.1-packed.js

jquery.carouFredSel-6.2.1-packed.js

215 ms

timetable.js

timetable.js

213 ms

qode-like.min.js

qode-like.min.js

228 ms

accordion.min.js

accordion.min.js

234 ms

position.min.js

position.min.js

233 ms

menu.min.js

menu.min.js

228 ms

wp-polyfill.min.js

wp-polyfill.min.js

228 ms

dom-ready.min.js

dom-ready.min.js

220 ms

a11y.min.js

a11y.min.js

220 ms

autocomplete.min.js

autocomplete.min.js

222 ms

button.min.js

button.min.js

216 ms

datepicker.min.js

datepicker.min.js

219 ms

mouse.min.js

mouse.min.js

211 ms

resizable.min.js

resizable.min.js

210 ms

draggable.min.js

draggable.min.js

212 ms

dialog.min.js

dialog.min.js

212 ms

droppable.min.js

droppable.min.js

206 ms

progressbar.min.js

progressbar.min.js

205 ms

css

css

212 ms

selectable.min.js

selectable.min.js

203 ms

sortable.min.js

sortable.min.js

322 ms

slider.min.js

slider.min.js

279 ms

spinner.min.js

spinner.min.js

276 ms

tooltip.min.js

tooltip.min.js

309 ms

effect.min.js

effect.min.js

202 ms

effect-blind.min.js

effect-blind.min.js

202 ms

effect-bounce.min.js

effect-bounce.min.js

203 ms

effect-clip.min.js

effect-clip.min.js

200 ms

effect-drop.min.js

effect-drop.min.js

199 ms

effect-explode.min.js

effect-explode.min.js

201 ms

effect-fade.min.js

effect-fade.min.js

201 ms

effect-fold.min.js

effect-fold.min.js

200 ms

effect-highlight.min.js

effect-highlight.min.js

218 ms

effect-pulsate.min.js

effect-pulsate.min.js

214 ms

effect-size.min.js

effect-size.min.js

213 ms

effect-scale.min.js

effect-scale.min.js

196 ms

effect-shake.min.js

effect-shake.min.js

196 ms

effect-slide.min.js

effect-slide.min.js

196 ms

effect-transfer.min.js

effect-transfer.min.js

199 ms

jquery.carouFredSel-6.2.1.min.js

jquery.carouFredSel-6.2.1.min.js

198 ms

lemmon-slider.min.js

lemmon-slider.min.js

193 ms

jquery.fullPage.min.js

jquery.fullPage.min.js

193 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

193 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

193 ms

packery-mode.pkgd.min.js

packery-mode.pkgd.min.js

195 ms

jquery.stretch.js

jquery.stretch.js

194 ms

imagesloaded.js

imagesloaded.js

192 ms

TweenLite.min.js

TweenLite.min.js

191 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

191 ms

smoothPageScroll.min.js

smoothPageScroll.min.js

191 ms

default_dynamic.js

default_dynamic.js

205 ms

custom_js.js

custom_js.js

205 ms

comment-reply.min.js

comment-reply.min.js

203 ms

js_composer_front.min.js

js_composer_front.min.js

203 ms

wp-embed.min.js

wp-embed.min.js

202 ms

script-min.js

script-min.js

84 ms

lannonstone-7.png

lannonstone-7.png

168 ms

logo.png

logo.png

94 ms

logo_black.png

logo_black.png

166 ms

lannonstoneicon.png

lannonstoneicon.png

165 ms

lannonstone-8.png

lannonstone-8.png

168 ms

lannonstone-8.png

lannonstone-8.png

166 ms

ga.js

ga.js

44 ms

262451130

262451130

121 ms

miners.jpg

miners.jpg

493 ms

mission.jpg

mission.jpg

493 ms

core.jpg

core.jpg

494 ms

img-noise-361x370.png

img-noise-361x370.png

493 ms

employeelogin-1.png

employeelogin-1.png

491 ms

loadcalculator-3.png

loadcalculator-3.png

490 ms

lannonstone-7.png

lannonstone-7.png

323 ms

lannonstone-8.png

lannonstone-8.png

404 ms

player.js

player.js

398 ms

player.css

player.css

302 ms

vuid.min.js

vuid.min.js

316 ms

__utm.gif

__utm.gif

248 ms

lannon-1.jpg

lannon-1.jpg

1123 ms

EJRLQgErUN8XuHNEtX81i9TmEkrnUchQ962a.ttf

EJRLQgErUN8XuHNEtX81i9TmEkrnUchQ962a.ttf

340 ms

JTURjIg1_i6t8kCHKm45_ZpC3gfD-w.ttf

JTURjIg1_i6t8kCHKm45_ZpC3gfD-w.ttf

255 ms

JTUSjIg1_i6t8kCHKm459Wdhzg.ttf

JTUSjIg1_i6t8kCHKm459Wdhzg.ttf

257 ms

JTURjIg1_i6t8kCHKm45_cJD3gfD-w.ttf

JTURjIg1_i6t8kCHKm45_cJD3gfD-w.ttf

256 ms

JTURjIg1_i6t8kCHKm45_aZA3gfD-w.ttf

JTURjIg1_i6t8kCHKm45_aZA3gfD-w.ttf

317 ms

JTUQjIg1_i6t8kCHKm45_QpRxy7j.ttf

JTUQjIg1_i6t8kCHKm45_QpRxy7j.ttf

317 ms

JTURjIg1_i6t8kCHKm45_bZF3gfD-w.ttf

JTURjIg1_i6t8kCHKm45_bZF3gfD-w.ttf

311 ms

JTURjIg1_i6t8kCHKm45_dJE3gfD-w.ttf

JTURjIg1_i6t8kCHKm45_dJE3gfD-w.ttf

310 ms

JTURjIg1_i6t8kCHKm45_c5H3gfD-w.ttf

JTURjIg1_i6t8kCHKm45_c5H3gfD-w.ttf

334 ms

JTURjIg1_i6t8kCHKm45_epG3gfD-w.ttf

JTURjIg1_i6t8kCHKm45_epG3gfD-w.ttf

335 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

676 ms

6951006_60x60.jpg

6951006_60x60.jpg

192 ms

sentry.js

sentry.js

41 ms

691726321.jpg

691726321.jpg

871 ms

wp-polyfill-fetch.min.js

wp-polyfill-fetch.min.js

212 ms

wp-polyfill-dom-rect.min.js

wp-polyfill-dom-rect.min.js

214 ms

wp-polyfill-url.min.js

wp-polyfill-url.min.js

323 ms

wp-polyfill-formdata.min.js

wp-polyfill-formdata.min.js

208 ms

wp-polyfill-element-closest.min.js

wp-polyfill-element-closest.min.js

210 ms

Accessibility Review

lannonstone.net accessibility score

69

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

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

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

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

lannonstone.net

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