9.4 sec in total
2 sec
6.8 sec
557 ms
Visit collective.works now to see the best up-to-date Collective content for Singapore and also check out these interesting facts you probably never knew about collective.works
Visit collective.worksWe analyzed Collective.works page load time and found that the first response time was 2 sec and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
collective.works performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value6.1 s
12/100
25%
Value4.2 s
77/100
10%
Value6,150 ms
0/100
30%
Value0.08
94/100
15%
Value11.8 s
17/100
10%
1960 ms
653 ms
436 ms
437 ms
39 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 79% of them (63 requests) were addressed to the original Collective.works, 4% (3 requests) were made to Googleadservices.com and 3% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Collective.works.
Page size can be reduced by 944.6 kB (36%)
2.7 MB
1.7 MB
In fact, the total size of Collective.works 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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 90.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 16.2 kB, which is 16% 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 90.6 kB or 87% of the original size.
Potential reduce by 4.8 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. Collective images are well optimized though.
Potential reduce by 536.4 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 536.4 kB or 60% of the original size.
Potential reduce by 312.8 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. Collective.works needs all CSS files to be minified and compressed as it can save up to 312.8 kB or 83% of the original size.
Number of requests can be reduced by 35 (47%)
74
39
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Collective. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.collective.works
1960 ms
wp-emoji-release.min.js
653 ms
styles.css
436 ms
se-styles.css
437 ms
css
39 ms
instag-slider.css
468 ms
jquery.js
1301 ms
jquery-migrate.min.js
654 ms
jquery.flexslider-min.js
900 ms
modernizr.custom.min.js
868 ms
daves-wordpress-live-search.css
869 ms
collective.min.css
2387 ms
font-awesome.min.css
34 ms
responsive.css
1300 ms
conversion.js
31 ms
jquery.min.js
59 ms
js
88 ms
collective.min.js
1367 ms
underscore.min.js
218 ms
daves-wordpress-live-search.min.js
366 ms
excanvas.compiled.js
368 ms
spinners.min.js
435 ms
jquery.form.min.js
753 ms
scripts.js
582 ms
scripts.js
800 ms
count.js
649 ms
analytics.js
15 ms
220 ms
logo.png
251 ms
mobile-logo.png
250 ms
mobile-edit.png
252 ms
mobile-search.png
250 ms
mobile-menu-btn.png
251 ms
close_nav.png
291 ms
small_spinner.gif
451 ms
Homepg_Featured-bar_Executive_lifestyle.png
448 ms
Homepg_Featured-bar_TechAsia.png
450 ms
Homepg_Featured-bar_Yahoo.png
452 ms
Homepg_Featured-bar_StraitTimes.png
449 ms
Homepg_Featured-bar_Asia.png
509 ms
channel5.png
665 ms
location-collectiveworks-cecil-street.jpg
1533 ms
location-collectiveworks-capitol-tower.jpg
1753 ms
Launching.jpg
666 ms
10727532_988240111287090_1521078350_n.jpg
887 ms
1515851_1042141649162852_472547106_n.jpg
723 ms
12317937_874818425970040_879479782_n.jpg
1098 ms
10413032_767076703436519_581362229_n.jpg
883 ms
12356603_1155983367768782_1496358429_n.jpg
942 ms
12345879_187563421591930_265759785_n.jpg
1318 ms
12362044_1037557682963589_1769868450_n.jpg
1542 ms
12277474_912957325425339_2051646788_n.jpg
1161 ms
12357751_733820300051224_1812192022_n.jpg
1533 ms
15thAnnualBusinessAwards.png
1379 ms
backtotop.png
1534 ms
phone.jpg
1595 ms
email.jpg
1749 ms
map.jpg
1753 ms
instagram.jpg
1755 ms
facebook.jpg
1761 ms
twitter.jpg
1813 ms
linkedin.jpg
1966 ms
vimeo.jpg
1965 ms
collect
152 ms
184 ms
fontawesome-webfont.woff
130 ms
1797718.js
282 ms
count.js
123 ms
Code_Pro_LC-webfont.woff
1760 ms
64 ms
38 ms
2C7321_2_0.woff
1726 ms
Code_Pro_Light_LC-webfont.woff
1739 ms
2C7321_1_0.woff
1939 ms
icons-spirit.png
1952 ms
43 ms
39 ms
collectiveworks-country-site.jpg
2551 ms
ajax-loader.gif
1755 ms
__ptq.gif
22 ms
collective.works 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
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
collective.works best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
collective.works SEO score
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 Collective.works 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 Collective.works 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.
collective.works
Open Graph description is not detected on the main page of Collective. 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: