5.2 sec in total
513 ms
4.4 sec
321 ms
Visit gobim.com now to see the best up-to-date Gobim content and also check out these interesting facts you probably never knew about gobim.com
Supply does not reinvent product data, it allows manufacturers to structure it via standardised templates to increase interoperability and data quality
Visit gobim.comWe analyzed Gobim.com page load time and found that the first response time was 513 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
gobim.com performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value16.7 s
0/100
25%
Value13.5 s
2/100
10%
Value1,030 ms
26/100
30%
Value0
100/100
15%
Value16.0 s
6/100
10%
513 ms
1752 ms
612 ms
637 ms
1062 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Gobim.com, 86% (59 requests) were made to Cobuilder.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Gobim.com.
Page size can be reduced by 235.6 kB (27%)
876.8 kB
641.2 kB
In fact, the total size of Gobim.com main page is 876.8 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. 55% of websites need less resources to load. Images take 604.8 kB which makes up the majority of the site volume.
Potential reduce by 189.9 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 189.9 kB or 87% of the original size.
Potential reduce by 13.5 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. Gobim images are well optimized though.
Potential reduce by 32.3 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 32.3 kB or 60% of the original size.
Number of requests can be reduced by 35 (56%)
63
28
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gobim. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
gobim.com
513 ms
gobim.com
1752 ms
select2.min.css
612 ms
iconfonts.css
637 ms
frontend.min.css
1062 ms
tooltip.css
693 ms
tooltipster-sideTip-shadow.min.css
757 ms
featherlight.css
735 ms
css
36 ms
lity.min.css
745 ms
mec-general-calendar.css
803 ms
style.min.css
945 ms
styles.css
949 ms
style.min.css
938 ms
f3105d1b28a9f2f3a8c10d08470e75eb.min.css
1386 ms
language-cookie.js
937 ms
jquery.min.js
1212 ms
mec-general-calendar.js
1464 ms
tooltip.js
1138 ms
frontend.js
1328 ms
events.js
1199 ms
iframeResizer.contentWindow.min.js
1316 ms
rs6.css
927 ms
core.min.js
824 ms
datepicker.min.js
1036 ms
jquery.typewatch.js
1057 ms
featherlight.js
1058 ms
select2.full.min.js
1075 ms
lity.min.js
1074 ms
colorbrightness.min.js
1058 ms
owl.carousel.min.js
1106 ms
rbtools.min.js
1327 ms
rs6.min.js
1480 ms
6c4cb4522f12ac7ca0f17e4b5fc929a5.min.js
1486 ms
gtm.js
164 ms
analytics.js
149 ms
l10cnmovl8
184 ms
Cobuilder-logo.svg
239 ms
Cobuilder-Link.svg
238 ms
Cobuilder-Collaborate.svg
279 ms
Cobuilder-Supply.svg
394 ms
Cobuilder-Connect.svg
396 ms
featured-solution-2.png
430 ms
Cobuilder-APIs.svg
501 ms
link-video-thumb3.png
905 ms
puzzle-peices-2.jpg
675 ms
Cobuilder-Solution-grey-v2.svg
556 ms
Cobuilder-Solutions-grey.svg
668 ms
skanska-logo.svg
664 ms
ncc-logo.svg
650 ms
standard-norge-logo.svg
688 ms
buildingSMART-logo.svg
777 ms
fib-logo.svg
791 ms
cerib-logo.svg
787 ms
genuit-group-logo.svg
789 ms
gs1-logo.svg
807 ms
bsi-logo-1.svg
887 ms
thomas-ingvaldsen-2.jpg
898 ms
thomas-ingvaldsen-article-quote.jpg
909 ms
Oppstartsmote-for-CIRPASS-2-pilotprosjektet-for-byggenaeringen.jpg
1059 ms
DataTemplate.png
927 ms
font
56 ms
fa-solid-900.woff
906 ms
fa-regular-400.woff
924 ms
fa-brands-400.woff
963 ms
js
37 ms
clarity.js
17 ms
awb-icons.woff
508 ms
c.gif
8 ms
gobim.com accessibility score
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
gobim.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
gobim.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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gobim.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 Gobim.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.
gobim.com
Open Graph data is detected on the main page of Gobim. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: