Tools & Wizards About Us
lineto.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

lineto.com

Lineto.com

Page Load Speed

2.7 sec in total

First Response

363 ms

Resources Loaded

2.2 sec

Page Rendered

91 ms

lineto.com screenshot

About Website

Visit lineto.com now to see the best up-to-date Lineto content for Switzerland and also check out these interesting facts you probably never knew about lineto.com

Lineto Type Foundry

Visit lineto.com

Key Findings

We analyzed Lineto.com page load time and found that the first response time was 363 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

lineto.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value2,670 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

lineto.com

363 ms

gui

187 ms

loader.html

197 ms

gui.css

182 ms

button.css

183 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that all of those requests were addressed to Lineto.com and no external sources were called. The less responsive or slowest element that took the longest time to load (623 ms) belongs to the original domain Lineto.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 107.1 kB (71%)

Content Size

151.4 kB

After Optimization

44.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lineto.com main page is 151.4 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. 15% of websites need less resources to load. Javascripts take 140.0 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 1.3 kB

  • Original 1.9 kB
  • After minification 1.9 kB
  • After compression 609 B

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 1.3 kB or 68% of the original size.

Image Optimization

-1%

Potential reduce by 56 B

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

JavaScript Optimization

-74%

Potential reduce by 104.0 kB

  • Original 140.0 kB
  • After minification 110.7 kB
  • After compression 35.9 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 104.0 kB or 74% of the original size.

CSS Optimization

-66%

Potential reduce by 1.7 kB

  • Original 2.6 kB
  • After minification 2.1 kB
  • After compression 860 B

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. Lineto.com needs all CSS files to be minified and compressed as it can save up to 1.7 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 84 (82%)

Requests Now

102

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lineto. 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 as a result speed up the page load time.

Network Requests Diagram

lineto.com

lineto.com

363 ms

gui

gui

187 ms

loader.html

loader.html

197 ms

gui.css

gui.css

182 ms

button.css

button.css

183 ms

core.js

core.js

280 ms

event.js

event.js

188 ms

util.js

util.js

189 ms

loader.js

loader.js

198 ms

gui.js

gui.js

271 ms

finder.js

finder.js

273 ms

general.js

general.js

297 ms

tree.js

tree.js

299 ms

cart.js

cart.js

431 ms

expandUp.gif

expandUp.gif

92 ms

expandDown.gif

expandDown.gif

95 ms

collapseUp.gif

collapseUp.gif

94 ms

collapseDown.gif

collapseDown.gif

95 ms

end.gif

end.gif

96 ms

closeUp.gif

closeUp.gif

183 ms

closeDown.gif

closeDown.gif

183 ms

grip.gif

grip.gif

186 ms

expandUp.gif

expandUp.gif

188 ms

expandDown.gif

expandDown.gif

187 ms

collapseUp.gif

collapseUp.gif

243 ms

collapseDown.gif

collapseDown.gif

272 ms

end.gif

end.gif

273 ms

moreUp.gif

moreUp.gif

280 ms

moreDown.gif

moreDown.gif

280 ms

lessUp.gif

lessUp.gif

280 ms

lessDown.gif

lessDown.gif

339 ms

grip.gif

grip.gif

362 ms

expandUp.gif

expandUp.gif

363 ms

expandDown.gif

expandDown.gif

375 ms

collapseUp.gif

collapseUp.gif

373 ms

collapseDown.gif

collapseDown.gif

371 ms

end.gif

end.gif

436 ms

closeUp.gif

closeUp.gif

452 ms

closeDown.gif

closeDown.gif

453 ms

scrollDecUp.gif

scrollDecUp.gif

462 ms

scrollDecDown.gif

scrollDecDown.gif

463 ms

scrollIncUp.gif

scrollIncUp.gif

463 ms

scrollIncDown.gif

scrollIncDown.gif

531 ms

resize.gif

resize.gif

541 ms

expandUp.gif

expandUp.gif

542 ms

expandDown.gif

expandDown.gif

554 ms

collapseUp.gif

collapseUp.gif

557 ms

collapseDown.gif

collapseDown.gif

552 ms

end.gif

end.gif

623 ms

closeUp.gif

closeUp.gif

550 ms

closeDown.gif

closeDown.gif

548 ms

scrollDecUp.gif

scrollDecUp.gif

563 ms

scrollDecDown.gif

scrollDecDown.gif

564 ms

scrollIncUp.gif

scrollIncUp.gif

565 ms

scrollIncDown.gif

scrollIncDown.gif

579 ms

checkOnUp.gif

checkOnUp.gif

549 ms

checkOnDown.gif

checkOnDown.gif

550 ms

checkOffUp.gif

checkOffUp.gif

563 ms

checkOffDown.gif

checkOffDown.gif

565 ms

radioOnUp.gif

radioOnUp.gif

563 ms

radioOnDown.gif

radioOnDown.gif

580 ms

radioOffUp.gif

radioOffUp.gif

550 ms

radioOffDown.gif

radioOffDown.gif

557 ms

addUp.gif

addUp.gif

560 ms

addDown.gif

addDown.gif

561 ms

removeUp.gif

removeUp.gif

562 ms

removeDown.gif

removeDown.gif

574 ms

resize.gif

resize.gif

550 ms

1.png

1.png

563 ms

2.png

2.png

560 ms

3.png

3.png

559 ms

4.png

4.png

560 ms

5.png

5.png

566 ms

6.png

6.png

549 ms

7.png

7.png

569 ms

8.png

8.png

561 ms

9.png

9.png

561 ms

10.png

10.png

563 ms

11.png

11.png

560 ms

12.png

12.png

549 ms

13.png

13.png

577 ms

14.png

14.png

559 ms

15.png

15.png

559 ms

16.png

16.png

560 ms

17.png

17.png

554 ms

18.png

18.png

551 ms

19.png

19.png

576 ms

20.png

20.png

559 ms

21.png

21.png

559 ms

22.png

22.png

563 ms

23.png

23.png

548 ms

24.png

24.png

547 ms

25.png

25.png

575 ms

26.png

26.png

561 ms

27.png

27.png

560 ms

28.png

28.png

569 ms

29.png

29.png

549 ms

30.png

30.png

549 ms

31.png

31.png

573 ms

32.png

32.png

562 ms

33.png

33.png

563 ms

34.png

34.png

579 ms

35.png

35.png

549 ms

Accessibility Review

lineto.com accessibility score

72

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

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

lineto.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

lineto.com SEO score

83

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lineto.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 Lineto.com main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

lineto.com

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