Tools & Wizards About Us
linpus.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 46

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

linpus.com

- Index - LINPUS

Page Load Speed

8.5 sec in total

First Response

880 ms

Resources Loaded

7.4 sec

Page Rendered

165 ms

linpus.com screenshot

About Website

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

- Index - LINPUS

Visit linpus.com

Key Findings

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

Performance Metrics

linpus.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.108

87/100

15%

TTI (Time to Interactive)

Value4.2 s

85/100

10%

Network Requests Diagram

page_index_en

880 ms

base.css

396 ms

style_tw.css

591 ms

cart_tw.css

591 ms

modified_tw.css

402 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 411.1 kB (18%)

Content Size

2.3 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Linpus.com main page is 2.3 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. 25% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 35.1 kB

  • Original 39.0 kB
  • After minification 22.0 kB
  • After compression 3.9 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 17.0 kB, which is 44% 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 35.1 kB or 90% of the original size.

Image Optimization

-4%

Potential reduce by 82.7 kB

  • Original 1.9 MB
  • After minification 1.8 MB

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. LINPUS images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 155.7 kB

  • Original 206.5 kB
  • After minification 161.1 kB
  • After compression 50.8 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 155.7 kB or 75% of the original size.

CSS Optimization

-89%

Potential reduce by 137.6 kB

  • Original 155.1 kB
  • After minification 117.2 kB
  • After compression 17.5 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. Linpus.com needs all CSS files to be minified and compressed as it can save up to 137.6 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (38%)

Requests Now

34

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

page_index_en

page_index_en

880 ms

base.css

base.css

396 ms

style_tw.css

style_tw.css

591 ms

cart_tw.css

cart_tw.css

591 ms

modified_tw.css

modified_tw.css

402 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

1908 ms

flyfreely.js

flyfreely.js

631 ms

jQueryRotate.js

jQueryRotate.js

995 ms

common.js

common.js

807 ms

owl.carousel.css

owl.carousel.css

991 ms

owl.theme.default.min.css

owl.theme.default.min.css

1005 ms

owl.carousel.js

owl.carousel.js

1444 ms

animate.css

animate.css

1588 ms

superfish.css

superfish.css

1386 ms

hoverIntent.js

hoverIntent.js

1393 ms

superfish.js

superfish.js

1413 ms

in_bg2.png

in_bg2.png

807 ms

scrolltop_button.png

scrolltop_button.png

402 ms

201605181004582_2.png

201605181004582_2.png

415 ms

201808281730512_0.jpg

201808281730512_0.jpg

4298 ms

201706291513482_0.jpg

201706291513482_0.jpg

1185 ms

201606291630513_0.jpg

201606291630513_0.jpg

1808 ms

201606241630192_2.png

201606241630192_2.png

804 ms

201606301009312_2.jpg

201606301009312_2.jpg

1394 ms

201606291457137_2.jpg

201606291457137_2.jpg

1595 ms

201606291358372_2.jpg

201606291358372_2.jpg

1601 ms

201606291344355_2.jpg

201606291344355_2.jpg

1985 ms

201606291329452_2.png

201606291329452_2.png

2382 ms

201606291318092_2.jpg

201606291318092_2.jpg

2397 ms

left.png

left.png

2010 ms

right.png

right.png

2213 ms

search_bar.png

search_bar.png

2388 ms

line_btn.png

line_btn.png

2406 ms

fb_btn.png

fb_btn.png

2602 ms

phone_btn.png

phone_btn.png

2779 ms

Accessibility Review

linpus.com accessibility score

46

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

SEO Factors

linpus.com SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Linpus.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Chinese language. Our system also found out that Linpus.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

linpus.com

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