Tools & Wizards About Us
briing.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

briing.com

Cheap international calls from UK landlines & mobiles - Briing.com

Page Load Speed

2 sec in total

First Response

51 ms

Resources Loaded

1.8 sec

Page Rendered

243 ms

briing.com screenshot

About Website

Click here to check amazing Briing content. Otherwise, check out these important facts you probably never knew about briing.com

Get cheap international phone calls with Briing.com - you can save on all calls to landlines & mobiles worldwide for less, using Briing's cheap and free international call services. Save money on text...

Visit briing.com

Key Findings

We analyzed Briing.com page load time and found that the first response time was 51 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

briing.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value1,130 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.049

99/100

15%

TTI (Time to Interactive)

Value15.8 s

6/100

10%

Network Requests Diagram

briing.com

51 ms

briing.com

207 ms

www.briing.com

27 ms

www.briing.com

257 ms

api.js

56 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 53% of them (33 requests) were addressed to the original Briing.com, 15% (9 requests) were made to Static.xx.fbcdn.net and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (909 ms) belongs to the original domain Briing.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 18.7 kB (4%)

Content Size

457.9 kB

After Optimization

439.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Briing.com main page is 457.9 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. 45% of websites need less resources to load. Images take 333.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 15.4 kB

  • Original 20.2 kB
  • After minification 20.2 kB
  • After compression 4.8 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 15.4 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 1.7 kB

  • Original 333.7 kB
  • After minification 332.1 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. Briing images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 271 B

  • Original 80.4 kB
  • After minification 80.4 kB
  • After compression 80.1 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

-6%

Potential reduce by 1.3 kB

  • Original 23.6 kB
  • After minification 23.6 kB
  • After compression 22.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. Briing.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

53

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

briing.com

briing.com

51 ms

briing.com

briing.com

207 ms

www.briing.com

www.briing.com

27 ms

www.briing.com

www.briing.com

257 ms

api.js

api.js

56 ms

jquery.dataTables.min.css

jquery.dataTables.min.css

69 ms

style.css

style.css

295 ms

slim-10_7.css

slim-10_7.css

36 ms

jquery.min.js

jquery.min.js

35 ms

bootstrap.min.js

bootstrap.min.js

62 ms

jquery.dataTables.min.js

jquery.dataTables.min.js

313 ms

buttons.js

buttons.js

39 ms

page.php

page.php

108 ms

logo.jpg

logo.jpg

244 ms

how-to.png

how-to.png

233 ms

australia-flag.png

australia-flag.png

244 ms

bangladesh-flag.png

bangladesh-flag.png

234 ms

brazil-flag.png

brazil-flag.png

388 ms

canada-flag.png

canada-flag.png

388 ms

china-flag.png

china-flag.png

388 ms

cyprus-flag.png

cyprus-flag.png

387 ms

france-flag.png

france-flag.png

389 ms

india-flag.png

india-flag.png

434 ms

ireland-flag.png

ireland-flag.png

565 ms

malaysia-flag.png

malaysia-flag.png

568 ms

new-zealand-flag.png

new-zealand-flag.png

569 ms

nigeria-flag.png

nigeria-flag.png

563 ms

pakistan-flag.png

pakistan-flag.png

567 ms

philippines-flag.png

philippines-flag.png

606 ms

poland-flag.png

poland-flag.png

736 ms

syria-flag.png

syria-flag.png

734 ms

south-africa-flag.png

south-africa-flag.png

740 ms

spain-flag.png

spain-flag.png

735 ms

thailand-flag.png

thailand-flag.png

743 ms

usa-flag.png

usa-flag.png

778 ms

zimbabwe-flag.png

zimbabwe-flag.png

909 ms

z1MHNwHMcp9.css

z1MHNwHMcp9.css

13 ms

SHojUHmeyWm.js

SHojUHmeyWm.js

20 ms

teTZ2tZqwkq.js

teTZ2tZqwkq.js

20 ms

D0hW5UcG2V4.js

D0hW5UcG2V4.js

64 ms

qnn7MVQZYOT.js

qnn7MVQZYOT.js

62 ms

7CmGfGBVS6H.js

7CmGfGBVS6H.js

63 ms

OWkNLphO4cA.js

OWkNLphO4cA.js

70 ms

p55HfXW__mM.js

p55HfXW__mM.js

62 ms

294314057_368048725461654_3127385597511888655_n.jpg

294314057_368048725461654_3127385597511888655_n.jpg

141 ms

294186020_368048728794987_2596380364487868816_n.jpg

294186020_368048728794987_2596380364487868816_n.jpg

388 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

18 ms

css

css

44 ms

call-landine.jpg

call-landine.jpg

852 ms

select-arrow.png

select-arrow.png

618 ms

call-mobile.jpg

call-mobile.jpg

697 ms

home-cnt-bg.png

home-cnt-bg.png

699 ms

analytics.js

analytics.js

25 ms

v2.zopim.com

v2.zopim.com

50 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

52 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

75 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

93 ms

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

91 ms

collect

collect

18 ms

asset_composer.js

asset_composer.js

69 ms

collect

collect

62 ms

js

js

99 ms

Accessibility Review

briing.com accessibility score

81

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

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

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

briing.com SEO score

83

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Briing.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 Briing.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

briing.com

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