Tools & Wizards About Us
brillins.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

brillins.com

Brillins Media || Brilliant Team, Outstanding Services

Page Load Speed

4.3 sec in total

First Response

278 ms

Resources Loaded

3.2 sec

Page Rendered

773 ms

brillins.com screenshot

About Website

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

Brillins is the name of quality and brilliance by which we accomplish our desired goals. Our web services, mobile app development, printing materials design, digital marketing, online logo design, and...

Visit brillins.com

Key Findings

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

Performance Metrics

brillins.com performance score

0

Network Requests Diagram

brillins.com

278 ms

brillins.com

512 ms

css

50 ms

css

61 ms

bootstrap.min.css

244 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 75% of them (50 requests) were addressed to the original Brillins.com, 6% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Brillins.com.

Page Optimization Overview & Recommendations

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

Content Size

1.8 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brillins.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. 50% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 20.8 kB

  • Original 27.4 kB
  • After minification 23.1 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 4.2 kB, which is 15% 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 20.8 kB or 76% of the original size.

Image Optimization

-17%

Potential reduce by 286.3 kB

  • Original 1.7 MB
  • After minification 1.4 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. Obviously, Brillins needs image optimization as it can save up to 286.3 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-6%

Potential reduce by 2.3 kB

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

CSS Optimization

-21%

Potential reduce by 5.7 kB

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

Requests Breakdown

Number of requests can be reduced by 18 (30%)

Requests Now

60

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brillins.com

brillins.com

278 ms

brillins.com

brillins.com

512 ms

css

css

50 ms

css

css

61 ms

bootstrap.min.css

bootstrap.min.css

244 ms

owl.carousel.min.css

owl.carousel.min.css

370 ms

djocistyle.css

djocistyle.css

370 ms

sepstiles.css

sepstiles.css

381 ms

animate.min.css

animate.min.css

61 ms

font-awesome.min.css

font-awesome.min.css

379 ms

js

js

101 ms

player.js

player.js

66 ms

jquery.min.js

jquery.min.js

632 ms

smoothscroll.js

smoothscroll.js

407 ms

bootstrap.min.js

bootstrap.min.js

650 ms

jquery.interactive_bg.js

jquery.interactive_bg.js

538 ms

owl.carousel.min.js

owl.carousel.min.js

539 ms

ie10-viewport-bug-workaround.js

ie10-viewport-bug-workaround.js

538 ms

modernizr.min.js

modernizr.min.js

72 ms

js

js

78 ms

analytics.js

analytics.js

74 ms

267464184

267464184

185 ms

cover.jpg

cover.jpg

880 ms

logo.png

logo.png

339 ms

1.png

1.png

869 ms

2.png

2.png

623 ms

3.png

3.png

359 ms

4.png

4.png

1111 ms

coffee.png

coffee.png

1234 ms

bg.png

bg.png

2000 ms

play.png

play.png

748 ms

web.png

web.png

874 ms

apps.png

apps.png

996 ms

support.png

support.png

1002 ms

broshure.png

broshure.png

1006 ms

p111.jpg

p111.jpg

1123 ms

p222.jpg

p222.jpg

1253 ms

p333.jpg

p333.jpg

1132 ms

p444.jpg

p444.jpg

1234 ms

p555.jpg

p555.jpg

1249 ms

s1.png

s1.png

1259 ms

s2.png

s2.png

1360 ms

s3.png

s3.png

1360 ms

s4.png

s4.png

1377 ms

a.png

a.png

1379 ms

c.png

c.png

1385 ms

icon3.png

icon3.png

1485 ms

bg7.jpg

bg7.jpg

1733 ms

bg1.png

bg1.png

1963 ms

s1s.png

s1s.png

1465 ms

s21.png

s21.png

1472 ms

s22.png

s22.png

1617 ms

s31.png

s31.png

1617 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf

78 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

94 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

101 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

100 ms

collect

collect

41 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1635 ms

s32.png

s32.png

1654 ms

s41.png

s41.png

1654 ms

collect

collect

27 ms

697993111-a855fd5f08f79f6f1b2b2dcbc515ee603faa8002be3b22d35ba5784c295a6085-d

697993111-a855fd5f08f79f6f1b2b2dcbc515ee603faa8002be3b22d35ba5784c295a6085-d

61 ms

s42.png

s42.png

1624 ms

bg3.jpg

bg3.jpg

1719 ms

tracking.js

tracking.js

34 ms

sep.png

sep.png

1575 ms

SEO Factors

brillins.com SEO score

0

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

brillins.com

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