Tools & Wizards About Us
brilens.com screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

brilens.com

Projector,Projector Manufacturer,Changsha Brilens Technology Co.,Ltd.

Page Load Speed

3.3 sec in total

First Response

407 ms

Resources Loaded

2.8 sec

Page Rendered

142 ms

brilens.com screenshot

About Website

Welcome to brilens.com homepage info - get ready to check Brilens best content right away, or after learning these important things about brilens.com

Projector,Projector Manufacturer—Changsha Brilens Technology Co.,Ltd. is a professional manufacturer on projector for 14 years

Visit brilens.com

Key Findings

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

Performance Metrics

brilens.com performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.11

87/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

brilens.com

407 ms

brilens.com

273 ms

www.brilens.com

523 ms

style.css

90 ms

jquery.js

263 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 87% of them (41 requests) were addressed to the original Brilens.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (997 ms) belongs to the original domain Brilens.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.4 kB (3%)

Content Size

2.7 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 17.2 kB

  • Original 21.7 kB
  • After minification 19.4 kB
  • After compression 4.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 2.4 kB, which is 11% 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 17.2 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 64.9 kB

  • Original 2.6 MB
  • After minification 2.5 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. Brilens images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 9.2 kB

  • Original 126.1 kB
  • After minification 125.9 kB
  • After compression 117.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-26%

Potential reduce by 4.2 kB

  • Original 16.0 kB
  • After minification 16.0 kB
  • After compression 11.7 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. Brilens.com needs all CSS files to be minified and compressed as it can save up to 4.2 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (56%)

Requests Now

43

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brilens.com

brilens.com

407 ms

brilens.com

brilens.com

273 ms

www.brilens.com

www.brilens.com

523 ms

style.css

style.css

90 ms

jquery.js

jquery.js

263 ms

js.js

js.js

205 ms

jquery-ui-1.9.2.custom.css

jquery-ui-1.9.2.custom.css

222 ms

index.css

index.css

216 ms

search_news1.js

search_news1.js

220 ms

jquery.min.js

jquery.min.js

334 ms

jquery.slides.min.js

jquery.slides.min.js

298 ms

returnTop.js

returnTop.js

298 ms

conversion.js

conversion.js

82 ms

analytics.js

analytics.js

26 ms

bg1.gif

bg1.gif

122 ms

logo01.jpg

logo01.jpg

631 ms

topemail.jpg

topemail.jpg

122 ms

6(2).jpg

6(2).jpg

552 ms

01banner.jpg

01banner.jpg

863 ms

banner01.jpg

banner01.jpg

881 ms

banner1.jpg

banner1.jpg

378 ms

worlddidacasia.jpg

worlddidacasia.jpg

764 ms

type1.jpg

type1.jpg

518 ms

typesee.png

typesee.png

597 ms

type2.jpg

type2.jpg

632 ms

type3.jpg

type3.jpg

703 ms

type4.jpg

type4.jpg

718 ms

aboutmore.jpg

aboutmore.jpg

702 ms

weima.png

weima.png

775 ms

footerlogo.jpg

footerlogo.jpg

781 ms

navli.jpg

navli.jpg

782 ms

MyriadSetPro-Semibold.ttf

MyriadSetPro-Semibold.ttf

997 ms

collect

collect

13 ms

js

js

79 ms

followbg.jpg

followbg.jpg

815 ms

follow1.png

follow1.png

799 ms

follow6.png

follow6.png

812 ms

follow2.png

follow2.png

880 ms

follow7.png

follow7.png

885 ms

follow3.png

follow3.png

885 ms

follow8.png

follow8.png

885 ms

abouttel.png

abouttel.png

886 ms

34 ms

st.png

st.png

89 ms

hotico.jpg

hotico.jpg

79 ms

bannerico.jpg

bannerico.jpg

70 ms

31 ms

Accessibility Review

brilens.com accessibility score

65

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

Best Practices

brilens.com best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

brilens.com SEO score

54

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brilens.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Brilens.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

brilens.com

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