Tools & Wizards About Us
losswise.com screenshot

Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

losswise.com

Losswise: Continuous Integration for Machine Learning

Page Load Speed

361 ms in total

First Response

30 ms

Resources Loaded

146 ms

Page Rendered

185 ms

losswise.com screenshot

About Website

Click here to check amazing Losswise content for United States. Otherwise, check out these important facts you probably never knew about losswise.com

Turn your GPUs into monitored build servers from a git push with Losswise. Interactive visualization, logs, smart notifications, and more. Start free today.

Visit losswise.com

Key Findings

We analyzed Losswise.com page load time and found that the first response time was 30 ms and then it took 331 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

losswise.com performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

93/100

10%

LCP (Largest Contentful Paint)

Value1.7 s

99/100

25%

SI (Speed Index)

Value1.6 s

100/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.8 s

100/100

10%

Network Requests Diagram

losswise.com

30 ms

losswise.com

43 ms

losswise.min.js

6 ms

losswise.css

7 ms

cloud.svg

22 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 62.3 kB (60%)

Content Size

103.0 kB

After Optimization

40.7 kB

  • HTML

In fact, the total size of Losswise.com main page is 103.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. 15% of websites need less resources to load. HTML takes 103.0 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 62.3 kB

  • Original 103.0 kB
  • After minification 102.0 kB
  • After compression 40.7 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 62.3 kB or 60% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

  • Images
  • JavaScript
  • CSS

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Losswise. According to our analytics all requests are already optimized.

Network Requests Diagram

losswise.com

losswise.com

30 ms

losswise.com

losswise.com

43 ms

losswise.min.js

losswise.min.js

6 ms

losswise.css

losswise.css

7 ms

cloud.svg

cloud.svg

22 ms

Accessibility Review

losswise.com accessibility score

65

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

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

SEO Factors

losswise.com SEO score

80

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

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

losswise.com

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