1.6 sec in total
192 ms
1.3 sec
129 ms
Visit wls.com now to see the best up-to-date Wls content and also check out these interesting facts you probably never knew about wls.com
Visit wls.comWe analyzed Wls.com page load time and found that the first response time was 192 ms and then it took 1.4 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.
wls.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value8.9 s
1/100
25%
Value4.5 s
73/100
10%
Value240 ms
85/100
30%
Value0.001
100/100
15%
Value7.2 s
51/100
10%
192 ms
72 ms
80 ms
73 ms
83 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 99% of them (143 requests) were addressed to the original Wls.com, 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (382 ms) belongs to the original domain Wls.com.
Page size can be reduced by 258.1 kB (80%)
322.7 kB
64.6 kB
In fact, the total size of Wls.com main page is 322.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. 70% of websites need less resources to load. Javascripts take 194.3 kB which makes up the majority of the site volume.
Potential reduce by 84.3 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. This page needs HTML code to be minified as it can gain 13.9 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 84.3 kB or 84% of the original size.
Potential reduce by 11 B
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. Wls images are well optimized though.
Potential reduce by 149.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 149.1 kB or 77% of the original size.
Potential reduce by 24.6 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. Wls.com needs all CSS files to be minified and compressed as it can save up to 24.6 kB or 93% of the original size.
Number of requests can be reduced by 21 (15%)
144
123
The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wls. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
wls.com
192 ms
SpryTabbedPanels.js
72 ms
SpryDOMUtils.js
80 ms
SpryDOMEffects.js
73 ms
SpryWidget.js
83 ms
SpryPanelSelector.js
56 ms
SpryPanelSet.js
92 ms
SpryFadingPanels.js
95 ms
SprySliderPanels.js
97 ms
SpryFilmStrip.js
107 ms
SpryImageLoader.js
104 ms
SpryImageSlideShow.js
140 ms
SpryThumbnailFilmStripPlugin.js
131 ms
SpryTitleSliderPlugin.js
129 ms
SpryPanAndZoomPlugin.js
131 ms
SpryAccordion.js
130 ms
SpryTabbedPanels.css
116 ms
basic_fs.css
150 ms
SpryAccordion.css
140 ms
ga.js
73 ms
combined.gif
46 ms
Welcomebutton.gif
42 ms
TrialButton.gif
46 ms
SrvcsBttn.gif
44 ms
hhbttn.gif
46 ms
ULBttn.gif
46 ms
AbtUsBttn.gif
60 ms
CUBttn.gif
63 ms
STButton.gif
63 ms
JC_inset_129.gif
140 ms
JC_Main_098.gif
116 ms
Lake-Quivira34-M_edit.gif
114 ms
Lake-Quivira66-i_edit.gif
137 ms
Lawrence-CC.gif
141 ms
Lawrence-CC-1.gif
139 ms
Lawrence-CC-2.gif
193 ms
Mission-Hills3_edit.gif
193 ms
Mission-Hills42_edit.gif
213 ms
Mission-Hills60_edit.gif
216 ms
busy.gif
177 ms
nav-left.png
166 ms
play.png
193 ms
nav-right.png
204 ms
arrow-left.png
218 ms
arrow-right.png
217 ms
slideshowheading.gif
229 ms
arrow.gif
229 ms
SEEDMAN-box.gif
237 ms
ProductsHeadline.gif
249 ms
EBluegrassButton.gif
242 ms
Fescues.gif
243 ms
Ryegrasses.gif
254 ms
Bentgrasses.gif
255 ms
Bermuda-Grasses.gif
261 ms
Wildflowers.gif
266 ms
AdditionalProd.gif
268 ms
__utm.gif
13 ms
EliteBluegrassHeading.gif
239 ms
CommonBluegrasses.gif
266 ms
RoughBluegrasses.gif
244 ms
TexasHybridBluegrasses.gif
251 ms
FineFescues.gif
258 ms
FescueBlends.gif
258 ms
FescueBlends2.gif
250 ms
PerennialRyegrasses.gif
252 ms
Bentgrasses-Certified.gif
277 ms
Bermudagrasses.gif
214 ms
Wildflowerheadline.gif
214 ms
wildflower,-baby-b-&-bloomers,-pst,-6-05b.gif
302 ms
bloomers.gif
325 ms
Wildflower,-Baby-B-&-Bloomers,-PST,-6-05c1.gif
331 ms
Wildflower,-Baby-B-&-Bloomers,-PST,-6-05c2.gif
343 ms
bloomers-1.gif
320 ms
AdditionProds.gif
230 ms
MiscItems.gif
243 ms
ServiceHeading.gif
278 ms
SEEDMAN-box-Srvcs.gif
281 ms
B-Mbutton.gif
285 ms
Packagingbutton.gif
284 ms
CompanyPoliciesButton.gif
283 ms
B-LInfo.gif
308 ms
PackagingInfo.gif
330 ms
Policies.gif
308 ms
HelpfulHintsHeading.gif
294 ms
SeedingRates.gif
282 ms
VarietyDefinitions.gif
278 ms
AnalysisTag.gif
302 ms
SeedCalculator.gif
300 ms
FAQ.gif
294 ms
SeedingRatesInfo.gif
347 ms
Zonesbutton.gif
300 ms
PRButton.gif
306 ms
KBButton.gif
306 ms
TFButton.gif
301 ms
ARButton.gif
297 ms
FFButton.gif
300 ms
PTButton.gif
305 ms
Bentgrassbutton.gif
312 ms
Zonemap.gif
350 ms
SEEDMAN-boxcombined-hh.gif
299 ms
PerennialRyegrassesInfo.gif
334 ms
kentuckybluegrass.gif
343 ms
tallfescue.gif
331 ms
annualryegrassinfo.gif
297 ms
finefescueinfo.gif
258 ms
Poa-Trivialis.gif
228 ms
BentgrassInfo.gif
281 ms
Analysistagepic.gif
382 ms
SEEDMAN-box-at.gif
230 ms
DeluxeHeading.gif
218 ms
SEEDMAN-boxcombined-Calculator.gif
227 ms
Revolution.gif
211 ms
Summer.gif
238 ms
ProTurf.gif
234 ms
VIP.gif
231 ms
Fairway.gif
231 ms
wateringtable.gif
222 ms
UsefulLinksHeading.gif
226 ms
University.gif
226 ms
SEEDMAN-box-UL.gif
227 ms
National.gif
227 ms
tgwca.gif
222 ms
AboutUsHeading.gif
227 ms
BckgrdInfo.gif
227 ms
SalesReps.gif
228 ms
garvinpic.gif
227 ms
leonpic2.gif
220 ms
garvinpic2.gif
230 ms
LeonPic.gif
229 ms
BillPic.gif
229 ms
DennisPic.gif
228 ms
SEEDMAN-boxcombined-CU.gif
224 ms
ContactUsHeading.gif
226 ms
SpecialThanksHeading.gif
229 ms
TurfMerchants.gif
224 ms
mvseed_logo.gif
213 ms
PickSeed.gif
209 ms
GrasslandOregon.gif
202 ms
tee2green-logo.gif
205 ms
oregrowseeds.gif
202 ms
A_Logo.gif
207 ms
DLF.gif
205 ms
Lewis.gif
193 ms
SEEDMAN-boxcombined.gif
28 ms
pause.png
28 ms
wls.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
wls.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
wls.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wls.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Wls.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.
wls.com
Open Graph description is not detected on the main page of Wls. 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: