Tools & Wizards About Us
comlax.net screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

comlax.net

Lacrosse Equipment: Sticks, Helmets & More Lacrosse Gear

Page Load Speed

1.2 sec in total

First Response

87 ms

Resources Loaded

1.1 sec

Page Rendered

89 ms

comlax.net screenshot

About Website

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

Lacrosse Equipment: Sticks, Helmets & More Lacrosse Gear | Shop ComLaxe for all your Lacrosse Head, Shaft, Cleat, Helmet & Protective Equipment needs from Top Brands like Brine, STX, Warrior, Cascade,...

Visit comlax.net

Key Findings

We analyzed Comlax.net page load time and found that the first response time was 87 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

comlax.net performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value1,580 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

comlax.net

87 ms

comlax.com

121 ms

comlax.purehockey.com

311 ms

site.css

20 ms

script-tag.js

39 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Comlax.net, 38% (8 requests) were made to Comlax.purehockey.com and 10% (2 requests) were made to Media.purehockey.com. The less responsive or slowest element that took the longest time to load (311 ms) relates to the external source Comlax.purehockey.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 146.5 kB (43%)

Content Size

340.0 kB

After Optimization

193.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Comlax.net main page is 340.0 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. 35% of websites need less resources to load. Javascripts take 190.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 23.8 kB

  • Original 31.3 kB
  • After minification 19.5 kB
  • After compression 7.6 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 11.8 kB, which is 38% 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 23.8 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 118.2 kB
  • After minification 118.2 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. Comlax images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 122.8 kB

  • Original 190.4 kB
  • After minification 190.4 kB
  • After compression 67.7 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 122.8 kB or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (59%)

Requests Now

17

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

comlax.net

comlax.net

87 ms

comlax.com

comlax.com

121 ms

comlax.purehockey.com

comlax.purehockey.com

311 ms

site.css

site.css

20 ms

script-tag.js

script-tag.js

39 ms

comlax_hero_main_logo.svg

comlax_hero_main_logo.svg

167 ms

comlax-homepage-banner-not-accepting-orders.png

comlax-homepage-banner-not-accepting-orders.png

148 ms

rocket-loader.min.js

rocket-loader.min.js

16 ms

Tracker.aspx

Tracker.aspx

215 ms

sezzle-logo-color-white-50px.png

sezzle-logo-color-white-50px.png

169 ms

script.js

script.js

28 ms

main.js

main.js

10 ms

js

js

151 ms

custom.js

custom.js

259 ms

sv.js

sv.js

38 ms

fbevents.js

fbevents.js

36 ms

jquery.js

jquery.js

109 ms

ai.3.gbl.min.js

ai.3.gbl.min.js

131 ms

barlow-regular.woff

barlow-regular.woff

237 ms

track.sv.rkdms.com

track.sv.rkdms.com

160 ms

site.js

site.js

109 ms

Accessibility Review

comlax.net accessibility score

77

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

[aria-*] attributes do not match their roles

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

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

comlax.net SEO score

86

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

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

comlax.net

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