Tools & Wizards About Us
liteline.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

liteline.com

Liteline - Home - Canada’s leading lighting manufacturer

Page Load Speed

3.8 sec in total

First Response

86 ms

Resources Loaded

2.2 sec

Page Rendered

1.5 sec

liteline.com screenshot

About Website

Welcome to liteline.com homepage info - get ready to check Liteline best content for Canada right away, or after learning these important things about liteline.com

Designed for easy installation, project economics, and with quality manufacturing, Liteline has the perfect solution for commercial and residential builds.

Visit liteline.com

Key Findings

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

liteline.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.1 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

liteline.com

86 ms

www.liteline.com

66 ms

www.liteline.com

384 ms

fastclick.js

73 ms

jquery.1.11.1.min.js

119 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 88% of them (89 requests) were addressed to the original Liteline.com, 5% (5 requests) were made to Livehelpnow.net and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (879 ms) belongs to the original domain Liteline.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (59%)

Content Size

3.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Liteline.com main page is 3.7 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. 65% of websites need less resources to load. Javascripts take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 71.2 kB

  • Original 83.8 kB
  • After minification 62.7 kB
  • After compression 12.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 21.1 kB, which is 25% 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 71.2 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 2.1 kB

  • Original 918.1 kB
  • After minification 916.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. Liteline images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 1.4 MB

  • Original 1.8 MB
  • After minification 1.7 MB
  • After compression 431.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 1.4 MB or 76% of the original size.

CSS Optimization

-82%

Potential reduce by 723.6 kB

  • Original 887.0 kB
  • After minification 842.2 kB
  • After compression 163.4 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. Liteline.com needs all CSS files to be minified and compressed as it can save up to 723.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 73 (78%)

Requests Now

93

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

liteline.com

liteline.com

86 ms

www.liteline.com

www.liteline.com

66 ms

www.liteline.com

www.liteline.com

384 ms

fastclick.js

fastclick.js

73 ms

jquery.1.11.1.min.js

jquery.1.11.1.min.js

119 ms

staticFunctions.js

staticFunctions.js

134 ms

ntnstore_master.js

ntnstore_master.js

111 ms

controls.js

controls.js

134 ms

utilities.js

utilities.js

135 ms

bootstrap.min.js

bootstrap.min.js

136 ms

default.css

default.css

242 ms

jquery-ui.css

jquery-ui.css

142 ms

jquery.ui.autocomplete.css

jquery.ui.autocomplete.css

151 ms

jquery-ui.css

jquery-ui.css

29 ms

js

js

83 ms

jquery-ui.min.js

jquery-ui.min.js

152 ms

jquery-ui-1.10.3.min.js

jquery-ui-1.10.3.min.js

224 ms

suggestsearch.js

suggestsearch.js

156 ms

lhnhelpouttab-current.min.js

lhnhelpouttab-current.min.js

92 ms

lhn-smsbutton.js

lhn-smsbutton.js

98 ms

WebResource.axd

WebResource.axd

164 ms

AdapterUtils.js

AdapterUtils.js

173 ms

MenuAdapter.js

MenuAdapter.js

173 ms

ScriptResource.axd

ScriptResource.axd

181 ms

ScriptResource.axd

ScriptResource.axd

186 ms

ScriptResource.axd

ScriptResource.axd

194 ms

www.liteline.com

www.liteline.com

879 ms

ScriptResource.axd

ScriptResource.axd

202 ms

ScriptResource.axd

ScriptResource.axd

209 ms

aos.js

aos.js

173 ms

llc_homepage2020.js

llc_homepage2020.js

181 ms

animate.min.css

animate.min.css

56 ms

luna.min.2023.css

luna.min.2023.css

54 ms

forum.min.css

forum.min.css

51 ms

klick.min.css

klick.min.css

52 ms

helios.min.css

helios.min.css

58 ms

llc40.min.css

llc40.min.css

83 ms

llc_sigma.min.css

llc_sigma.min.css

74 ms

markets_national.min.css

markets_national.min.css

81 ms

brochures.min.css

brochures.min.css

76 ms

flex.min.css

flex.min.css

82 ms

llc_home.min.css

llc_home.min.css

95 ms

edge.css

edge.css

96 ms

quickship.min.css

quickship.min.css

97 ms

spex.min.css

spex.min.css

97 ms

productfinder.css

productfinder.css

98 ms

all.css

all.css

74 ms

css

css

67 ms

pastwebinars.css

pastwebinars.css

116 ms

precisionpro.css

precisionpro.css

117 ms

track_v2.css

track_v2.css

121 ms

slimled.css

slimled.css

119 ms

genesis.css

genesis.css

122 ms

oncloud.css

oncloud.css

137 ms

homepage2023.min.css

homepage2023.min.css

140 ms

discover.css

discover.css

140 ms

inspire.css

inspire.css

143 ms

oncloudFAQ.css

oncloudFAQ.css

142 ms

title24ja8.css

title24ja8.css

161 ms

luna56Pro.min.css

luna56Pro.min.css

163 ms

tape.min.css

tape.min.css

161 ms

oncloud-certification.css

oncloud-certification.css

164 ms

slimled_multi.min.css

slimled_multi.min.css

164 ms

shade_mini.min.css

shade_mini.min.css

181 ms

fire-rated.min.css

fire-rated.min.css

185 ms

glareguides.min.css

glareguides.min.css

182 ms

orbit.min.css

orbit.min.css

185 ms

track_heads.min.css

track_heads.min.css

147 ms

sustainability.min.css

sustainability.min.css

159 ms

lunapro.min.css

lunapro.min.css

158 ms

tape_channels.min.css

tape_channels.min.css

157 ms

2.ac73090f.chunk.css

2.ac73090f.chunk.css

155 ms

main.b3297660.chunk.css

main.b3297660.chunk.css

157 ms

aos.css

aos.css

152 ms

skrollr.css

skrollr.css

128 ms

liteline_logo_horizontal.gif

liteline_logo_horizontal.gif

68 ms

Liteline_favicon.png

Liteline_favicon.png

66 ms

hoverimage2_Flex-DualHead-WallSconce.jpg

hoverimage2_Flex-DualHead-WallSconce.jpg

68 ms

hoverimage2A_Flex-DualHead-WallSconce.jpg

hoverimage2A_Flex-DualHead-WallSconce.jpg

68 ms

hoverimage3_GenesisSquare.jpg

hoverimage3_GenesisSquare.jpg

70 ms

hoverimage3A_GenesisSquare.jpg

hoverimage3A_GenesisSquare.jpg

68 ms

hoverimage1_lunafire.jpg

hoverimage1_lunafire.jpg

70 ms

hoverimage1b_lunafire.jpg

hoverimage1b_lunafire.jpg

71 ms

bannerIMG_sustainability.jpg

bannerIMG_sustainability.jpg

71 ms

save2.png

save2.png

69 ms

RA56_SLWH.jpg

RA56_SLWH.jpg

71 ms

logo_warranty_lifetime.svg

logo_warranty_lifetime.svg

132 ms

WBC-bldg-4.jpg

WBC-bldg-4.jpg

139 ms

leaf_canada.png

leaf_canada.png

135 ms

bannerIMG_quickship.jpg

bannerIMG_quickship.jpg

137 ms

logoIMG_quickship.png

logoIMG_quickship.png

136 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

66 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

66 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

67 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

64 ms

banner23_delta.jpg

banner23_delta.jpg

125 ms

1-WORK.jpg

1-WORK.jpg

175 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

33 ms

livehelpnow.min.aspx

livehelpnow.min.aspx

80 ms

helppanel.ashx

helppanel.ashx

79 ms

style.css

style.css

80 ms

Accessibility Review

liteline.com accessibility score

88

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

liteline.com SEO score

82

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    EN

  • Encoding

    UTF-8

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

liteline.com

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