1.4 sec in total
265 ms
958 ms
147 ms
Visit bright.ly now to see the best up-to-date Bright content and also check out these interesting facts you probably never knew about bright.ly
Bright.ly is the first Italian independent agency, specialized in converging digital communication: tv+web+mobile.
Visit bright.lyWe analyzed Bright.ly page load time and found that the first response time was 265 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
bright.ly performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value7.0 s
6/100
25%
Value8.7 s
16/100
10%
Value220 ms
87/100
30%
Value0.036
100/100
15%
Value7.1 s
51/100
10%
265 ms
195 ms
6 ms
286 ms
179 ms
Our browser made a total of 20 requests to load all elements on the main page. We found that 45% of them (9 requests) were addressed to the original Bright.ly, 20% (4 requests) were made to F.vimeocdn.com and 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (639 ms) belongs to the original domain Bright.ly.
Page size can be reduced by 368.1 kB (45%)
819.7 kB
451.6 kB
In fact, the total size of Bright.ly main page is 819.7 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. 35% of websites need less resources to load. Javascripts take 359.2 kB which makes up the majority of the site volume.
Potential reduce by 5.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 1.7 kB, which is 22% 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 5.5 kB or 69% of the original size.
Potential reduce by 4.6 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. Bright images are well optimized though.
Potential reduce by 233.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 233.6 kB or 65% of the original size.
Potential reduce by 124.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. Bright.ly needs all CSS files to be minified and compressed as it can save up to 124.5 kB or 87% of the original size.
Number of requests can be reduced by 6 (33%)
18
12
The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bright. 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 as a result speed up the page load time.
bright.ly
265 ms
style.css
195 ms
jquery.min.js
6 ms
script.js
286 ms
fitvids.js
179 ms
logo.png
271 ms
Thumb_Lancia_qgtufnz7.jpg
379 ms
thumb_Ortie_uyjw24go.jpg
639 ms
thumb_wearmanijeans_msw8p42n.jpg
619 ms
ga.js
13 ms
social.woff
106 ms
__utm.gif
41 ms
59396131
83 ms
player.js
104 ms
player.css
87 ms
ga.js
27 ms
vuid.min.js
100 ms
__utm.gif
30 ms
proxy.html
35 ms
413366956.jpg
125 ms
bright.ly accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
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.
bright.ly 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
bright.ly SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bright.ly 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 Bright.ly main page’s claimed encoding is utf8. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
bright.ly
Open Graph description is not detected on the main page of Bright. 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: