4.3 sec in total
411 ms
3.5 sec
373 ms
Visit qbrick.com now to see the best up-to-date Qbrick content for Sri Lanka and also check out these interesting facts you probably never knew about qbrick.com
Take the leap towards building a more professional online video strategy, with secure hosting, modern presentation & advanced functionality.
Visit qbrick.comWe analyzed Qbrick.com page load time and found that the first response time was 411 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
qbrick.com performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value7.0 s
6/100
25%
Value38.4 s
0/100
10%
Value17,720 ms
0/100
30%
Value0.039
100/100
15%
Value42.2 s
0/100
10%
411 ms
629 ms
25 ms
38 ms
45 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Qbrick.com, 58% (54 requests) were made to Arkena.com and 8% (7 requests) were made to Play.arkena.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Arkena.com.
Page size can be reduced by 765.0 kB (49%)
1.6 MB
797.3 kB
In fact, the total size of Qbrick.com main page is 1.6 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. 55% of websites need less resources to load. Javascripts take 703.0 kB which makes up the majority of the site volume.
Potential reduce by 55.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 55.5 kB or 82% of the original size.
Potential reduce by 38.4 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. Qbrick images are well optimized though.
Potential reduce by 485.6 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 485.6 kB or 69% of the original size.
Potential reduce by 185.6 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. Qbrick.com needs all CSS files to be minified and compressed as it can save up to 185.6 kB or 85% of the original size.
Number of requests can be reduced by 49 (59%)
83
34
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qbrick. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
qbrick.com
411 ms
www.arkena.com
629 ms
css
25 ms
css
38 ms
satelliteLib-9859ab225a486eac6d53f83ccfeb945dc1208746-staging.js
45 ms
language-selector.css
173 ms
arkena-player.css
170 ms
style.css
180 ms
settings.css
188 ms
pagenavi-css.css
182 ms
arkena.min.css
200 ms
styles.min.css
335 ms
jquery.fancybox-1.3.7.min.css
342 ms
jquery.min.js
34 ms
jquery.themepunch.tools.min.js
435 ms
jquery.themepunch.revolution.min.js
447 ms
jquery.js
509 ms
fastclick.js
517 ms
foundation.min.js
519 ms
playerembed.js
723 ms
arkena.min.js
527 ms
underscore.min.js
599 ms
daves-wordpress-live-search.min.js
612 ms
excanvas.compiled.js
642 ms
spinners.min.js
663 ms
script.min.js
672 ms
sitepress.js
670 ms
count.js
765 ms
jquery.fancybox-1.3.7.min.js
788 ms
jquery.easing.pack.js
804 ms
jquery.mousewheel.min.js
831 ms
css
17 ms
123780
296 ms
play_button.png
347 ms
ccd25
526 ms
sprite_logo.png
469 ms
search.png
470 ms
arkena-site-background-v3-light.jpg
726 ms
universal.png
471 ms
beinsports.png
494 ms
disney.png
523 ms
FOX_logo.png
548 ms
tf1.png
540 ms
technicolor.png
624 ms
arrow_left.png
655 ms
arrow_right.png
722 ms
jerome_lore.png
864 ms
play-icon.png
723 ms
trista_dulaz.png
1022 ms
lars-%C3%A5ke-johansson.jpg
833 ms
Stephanie-Holm-Fox-Int-150x150.jpg
847 ms
hero-image3.jpg
1132 ms
C4M.png
896 ms
CDN_icon.png
1022 ms
OTT.png
1007 ms
AVP.png
1019 ms
PLAY.png
1038 ms
MBP.png
1154 ms
Cabsat1.png
1220 ms
NexGuard.jpg
1244 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
19 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
30 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
55 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
47 ms
TVConnectAfrica.png
1168 ms
sprite_icons.png
1134 ms
EmbedHandler.ashx
633 ms
analytics.js
22 ms
s-code-contents-4b2ea3943b1d078c7a4ca4cddbd9f10c6fdf210c-staging.js
13 ms
2nps9y
398 ms
312 ms
207 ms
count.js
25 ms
collect
26 ms
s4140961830038
6 ms
play_button.png
177 ms
light-mask.png
1018 ms
form.css
159 ms
piUtils.js
9 ms
104 ms
pardot-form.css
704 ms
required.gif
157 ms
collect
10 ms
107 ms
134 ms
pd.js
5 ms
analytics
282 ms
PlayerHandler.ashx
1006 ms
PlayerHandler.ashx%3Faction%3Dgetskin%26embedId%3Dqbrick_professional_qbrick1%26mcid%3DD4BCE79450D45AA5%26width%3D640%26height%3D360%26as%3D0%26mid%3DD4BCE794%29%3B
1 ms
PlayerHandler.ashx
1094 ms
restriction_sorry.svg
126 ms
collect
10 ms
analytics
204 ms
qbrick.com accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
qbrick.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
qbrick.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qbrick.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 Qbrick.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.
qbrick.com
Open Graph data is detected on the main page of Qbrick. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: