19.8 sec in total
1.5 sec
18 sec
230 ms
Click here to check amazing Concatenum content. Otherwise, check out these important facts you probably never knew about concatenum.com
Visit concatenum.comWe analyzed Concatenum.com page load time and found that the first response time was 1.5 sec and then it took 18.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
concatenum.com performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value5.4 s
20/100
25%
Value4.4 s
74/100
10%
Value170 ms
93/100
30%
Value0.014
100/100
15%
Value4.0 s
88/100
10%
1544 ms
310 ms
297 ms
312 ms
294 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 16% of them (25 requests) were addressed to the original Concatenum.com, 28% (43 requests) were made to Static.xx.fbcdn.net and 26% (40 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (16 sec) belongs to the original domain Concatenum.com.
Page size can be reduced by 909.5 kB (28%)
3.2 MB
2.3 MB
In fact, the total size of Concatenum.com main page is 3.2 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. Only a small number of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 57.4 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 57.4 kB or 83% of the original size.
Potential reduce by 25.0 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. Concatenum images are well optimized though.
Potential reduce by 436.0 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 436.0 kB or 67% of the original size.
Potential reduce by 391.1 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. Concatenum.com needs all CSS files to be minified and compressed as it can save up to 391.1 kB or 60% of the original size.
Number of requests can be reduced by 83 (57%)
145
62
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Concatenum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 65 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
concatenum.com
1544 ms
wp-emoji-release.min.js
310 ms
25px.min.css
297 ms
gallery.min.css
312 ms
style.css
294 ms
style.css
297 ms
css
27 ms
css
38 ms
css
48 ms
jquery.js
420 ms
jquery-migrate.min.js
582 ms
platform.js
55 ms
in.js
13 ms
embed.js
16 ms
masonry.min.js
466 ms
script.js
466 ms
style.css
304 ms
secureAnonymousFramework
99 ms
concatenum-ibm360.jpg
344 ms
middle-earth-map.jpg
1116 ms
ainulindale.jpg
941 ms
nine_to_five.jpg
870 ms
evolucao_celulares_1060.jpg
753 ms
facebook-comunity-update-november-2015.jpg
870 ms
fioapp.jpg
939 ms
delorean.gif
1968 ms
iftt-data-infrastructure.jpeg
1198 ms
shortest-flight.jpg
1217 ms
informacao-conhecimento-conspiracao.jpg
1380 ms
nunca-pare-de-programar-1024x640.png
15959 ms
marcus-lemonis-ppp.jpg
1468 ms
sdk.js
35 ms
widgets.js
34 ms
6tmbeLTHC_0
222 ms
301 ms
blockquote.png
1452 ms
toadOcfmlt9b38dHJxOBGC-IiwWNzQT_LXAtr-Ee9Pw.woff
54 ms
ODelI1aHBYDBqgeIAH2zlNHq-FFgoDNV3GTKpHwuvtI.woff
117 ms
zhcz-_WihjSQC0oHJ9TCYL3hpw3pgy2gAi-Ip7WPMi0.woff
118 ms
IQHow_FEYlDC4Gzy_m8fcnbFhgvWbfSbdVg11QabG8w.woff
118 ms
7YGmE4Ls5b94ct65u07hVQLUuEpTyoUstqEm5AMlJo4.woff
119 ms
0XxGQsSc1g4rdRdjJKZrNL3hpw3pgy2gAi-Ip7WPMi0.woff
118 ms
embed-controller.js
39 ms
analytics.js
57 ms
135 ms
embed
217 ms
125 ms
xd_arbiter.php
142 ms
xd_arbiter.php
178 ms
www-embed-player-vflfNyN_r.css
95 ms
www-embed-player.js
112 ms
base.js
145 ms
collect
26 ms
interstate-0ab59479718c8235122cad6b16a66953d725c43a.css
443 ms
widget-0511d506.css
177 ms
widget-d9304090.js
372 ms
like.php
179 ms
like.php
132 ms
like.php
172 ms
like.php
219 ms
like.php
207 ms
like.php
232 ms
like.php
203 ms
imageViewerInline.js
131 ms
logo.png
137 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
115 ms
ad_status.js
115 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
106 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
108 ms
fNFEOa8-9dh.js
124 ms
LVx-xkvaJ0b.png
114 ms
like.php
124 ms
like.php
127 ms
like.php
289 ms
like.php
190 ms
like.php
188 ms
like.php
187 ms
lumbar.gif
81 ms
apple.png
31 ms
android.png
30 ms
lumbar.gif
80 ms
like.php
240 ms
like.php
210 ms
like.php
259 ms
like.php
235 ms
like.php
205 ms
like.php
294 ms
fNFEOa8-9dh.js
30 ms
fNFEOa8-9dh.js
78 ms
fNFEOa8-9dh.js
207 ms
fNFEOa8-9dh.js
196 ms
fNFEOa8-9dh.js
239 ms
fNFEOa8-9dh.js
239 ms
fNFEOa8-9dh.js
234 ms
logo-200x120-177df3dd.png
152 ms
ga.js
27 ms
visual-single-sound-cd67be80.js
71 ms
error-698b3c1d.js
42 ms
__utm.gif
75 ms
beacon.js
75 ms
__utm.gif
66 ms
like.php
84 ms
logo_grey-377f1b9e.png
52 ms
like.php
66 ms
like.php
121 ms
like.php
194 ms
like.php
132 ms
like.php
125 ms
like.php
94 ms
like.php
155 ms
like.php
175 ms
like.php
183 ms
like.php
203 ms
like.php
202 ms
fNFEOa8-9dh.js
20 ms
fNFEOa8-9dh.js
19 ms
fNFEOa8-9dh.js
16 ms
fNFEOa8-9dh.js
32 ms
like.php
169 ms
like.php
159 ms
like.php
240 ms
like.php
249 ms
like.php
260 ms
fNFEOa8-9dh.js
95 ms
fNFEOa8-9dh.js
93 ms
like.php
246 ms
fNFEOa8-9dh.js
89 ms
fNFEOa8-9dh.js
88 ms
fNFEOa8-9dh.js
87 ms
fNFEOa8-9dh.js
123 ms
fNFEOa8-9dh.js
122 ms
fNFEOa8-9dh.js
117 ms
fNFEOa8-9dh.js
153 ms
fNFEOa8-9dh.js
147 ms
fNFEOa8-9dh.js
153 ms
fNFEOa8-9dh.js
156 ms
like.php
183 ms
fNFEOa8-9dh.js
155 ms
fNFEOa8-9dh.js
152 ms
fNFEOa8-9dh.js
149 ms
fNFEOa8-9dh.js
145 ms
fNFEOa8-9dh.js
143 ms
fNFEOa8-9dh.js
136 ms
fNFEOa8-9dh.js
133 ms
fNFEOa8-9dh.js
128 ms
fNFEOa8-9dh.js
106 ms
fNFEOa8-9dh.js
102 ms
fNFEOa8-9dh.js
99 ms
fNFEOa8-9dh.js
95 ms
fNFEOa8-9dh.js
95 ms
fNFEOa8-9dh.js
91 ms
fNFEOa8-9dh.js
91 ms
fNFEOa8-9dh.js
88 ms
fNFEOa8-9dh.js
77 ms
fNFEOa8-9dh.js
73 ms
concatenum.com accessibility score
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
concatenum.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Page has valid source maps
concatenum.com 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
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Concatenum.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Portuguese language. Our system also found out that Concatenum.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.
concatenum.com
Open Graph description is not detected on the main page of Concatenum. 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: