26 sec in total
11.3 sec
14.6 sec
164 ms
Visit flog.cat now to see the best up-to-date Flog content for Spain and also check out these interesting facts you probably never knew about flog.cat
Xarxa social en català per a la gent jove dels Països Catalans, on connectar-te amb els teus amics, xat, carregar fotos, tenir el teu perfil, conèixer gent nova, fer noves amistats i compartir l'...
Visit flog.catWe analyzed Flog.cat page load time and found that the first response time was 11.3 sec and then it took 14.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
flog.cat performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value7.3 s
5/100
25%
Value12.0 s
4/100
10%
Value12,120 ms
0/100
30%
Value0.36
30/100
15%
Value22.2 s
1/100
10%
11276 ms
98 ms
238 ms
5 ms
143 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 58% of them (31 requests) were addressed to the original Flog.cat, 11% (6 requests) were made to Blogs.flog.cat and 9% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (11.3 sec) belongs to the original domain Flog.cat.
Page size can be reduced by 61.3 kB (36%)
170.4 kB
109.1 kB
In fact, the total size of Flog.cat main page is 170.4 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. 30% of websites need less resources to load. Javascripts take 85.5 kB which makes up the majority of the site volume.
Potential reduce by 10.8 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 10.8 kB or 69% of the original size.
Potential reduce by 4.9 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. Flog images are well optimized though.
Potential reduce by 45.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 45.6 kB or 53% of the original size.
Number of requests can be reduced by 32 (62%)
52
20
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
flog.cat
11276 ms
estil.css
98 ms
js.js
238 ms
show_ads.js
5 ms
ca-pub-9487418498099302.js
143 ms
zrt_lookup.html
138 ms
show_ads_impl.js
85 ms
140_9300_m2.jpg
1106 ms
image.php
3033 ms
sensefoto_m2.jpg
1086 ms
2530_8513_m2.jpg
1092 ms
2565_2225_m2.jpg
1092 ms
2559_4757_m2.jpg
2025 ms
2561_8229_m2.jpg
2024 ms
masthead.png
133 ms
logo.png
133 ms
m_gent.png
174 ms
m_grups.png
175 ms
m_blog.png
173 ms
m_piu.png
176 ms
m_fotos.png
175 ms
m_campanyes.png
174 ms
m_down.png
251 ms
m_jocs.png
250 ms
m_viucat.png
251 ms
m_forum.png
252 ms
m_xat.png
253 ms
login2.png
253 ms
star_smiley.png
329 ms
33afe97e23bbae09a68892ebea1de2fa_m.jpg
328 ms
b70ec7daf179224332cf66c9a5dfd884_m.jpg
329 ms
1a71f55e3dd1dfcae53a66ba90e09610_m.jpg
332 ms
321b6a0f9441c57a6f410ae141395ff2_m.jpg
334 ms
62ada5ee758d5cc2eb60e4f327f1ec74_m.jpg
334 ms
c2a6fba1b8dad24d5c1a5ff69186e903_m.jpg
407 ms
c12edf7b96e547d555339392e964d595_m.jpg
405 ms
f03dc8da1450c74305517bde5fb1008f_m.jpg
407 ms
e5e379c9ab483531de48bad9e19a779d_m.jpg
411 ms
ad3df2fe516a3895f1b7b1b176918fcf_p.jpg
412 ms
e2baa885ae5a42bfa1e184fcf0d096fe_m2.jpg
412 ms
star_smile.png
464 ms
piwik.js
282 ms
ads
322 ms
osd.js
16 ms
ads
275 ms
btbg.png
134 ms
515283939779265030
21 ms
abg.js
30 ms
m_js_controller.js
41 ms
googlelogo_color_112x36dp.png
72 ms
s
22 ms
x_button_blue2.png
22 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
3 ms
flog.cat 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
Image elements do not have [alt] attributes
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.
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.
flog.cat 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
flog.cat SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
CA
CA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flog.cat can be misinterpreted by Google and other search engines. Our service has detected that Catalan is used on the page, and it matches the claimed language. Our system also found out that Flog.cat 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.
flog.cat
Open Graph description is not detected on the main page of Flog. 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: