Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

73lines.com

Odoo and Flectra - CMS, Ecommerce Web Development & Design Company

Page Load Speed

4 sec in total

First Response

218 ms

Resources Loaded

3.5 sec

Page Rendered

257 ms

73lines.com screenshot

About Website

Click here to check amazing 73 Lines content for India. Otherwise, check out these important facts you probably never knew about 73lines.com

73Lines is highly focused Odoo and Flectra CMS, E-commerce and web development com

Visit 73lines.com

Key Findings

We analyzed 73lines.com page load time and found that the first response time was 218 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

73lines.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value1,640 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.105

88/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

73lines.com

218 ms

www.73lines.com

1672 ms

web.assets_common.0.css

205 ms

website.assets_frontend.0.css

710 ms

website.assets_frontend.1.css

472 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 88% of them (28 requests) were addressed to the original 73lines.com, 6% (2 requests) were made to Google-analytics.com and 6% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain 73lines.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (75%)

Content Size

1.8 MB

After Optimization

447.3 kB

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

HTML Optimization

-77%

Potential reduce by 32.4 kB

  • Original 41.8 kB
  • After minification 41.8 kB
  • After compression 9.5 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 32.4 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 3.5 kB

  • Original 63.8 kB
  • After minification 60.3 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. 73 Lines images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 848.8 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 305.2 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 848.8 kB or 74% of the original size.

CSS Optimization

-87%

Potential reduce by 492.4 kB

  • Original 564.7 kB
  • After minification 471.3 kB
  • After compression 72.3 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. 73lines.com needs all CSS files to be minified and compressed as it can save up to 492.4 kB or 87% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

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

Accessibility Review

73lines.com accessibility score

70

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

button, link, and menuitem elements do not have accessible names.

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

73lines.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

73lines.com SEO score

85

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

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 73lines.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 73lines.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

Open Graph data is detected on the main page of 73 Lines. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: