12.1 sec in total
2.8 sec
9 sec
258 ms
Click here to check amazing Sant Feliu content for Spain. Otherwise, check out these important facts you probably never knew about santfeliu.cat
Visit santfeliu.catWe analyzed Santfeliu.cat page load time and found that the first response time was 2.8 sec and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
santfeliu.cat performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value5.2 s
23/100
25%
Value7.8 s
24/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value5.7 s
68/100
10%
2826 ms
229 ms
236 ms
362 ms
226 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 97% of them (92 requests) were addressed to the original Santfeliu.cat, 2% (2 requests) were made to Scontent.xx.fbcdn.net and 1% (1 request) were made to 3.bp.blogspot.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Santfeliu.cat.
Page size can be reduced by 598.0 kB (67%)
888.2 kB
290.2 kB
In fact, the total size of Santfeliu.cat main page is 888.2 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. 20% of websites need less resources to load. Images take 269.0 kB which makes up the majority of the site volume.
Potential reduce by 134.7 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 134.7 kB or 77% of the original size.
Potential reduce by 84.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. Obviously, Sant Feliu needs image optimization as it can save up to 84.6 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 176.5 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 176.5 kB or 82% of the original size.
Potential reduce by 202.2 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. Santfeliu.cat needs all CSS files to be minified and compressed as it can save up to 202.2 kB or 88% of the original size.
Number of requests can be reduced by 33 (44%)
75
42
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sant Feliu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
go.faces
2826 ms
topframe.css
229 ms
frame.css
236 ms
template.css
362 ms
widget.css
226 ms
theme.css
454 ms
985083
2602 ms
985087
911 ms
common.js
361 ms
clock.js
473 ms
savescroll.js
115 ms
carousel.js
116 ms
widgetselector.js
1379 ms
prototype.js
1385 ms
builder.js
116 ms
effects.js
1003 ms
dragdrop.js
883 ms
widget.js
557 ms
widgetfold.js
1139 ms
1914572_1710568295824540_5680789231830003818_n.jpg
114 ms
especialss.JPG
194 ms
topbar.jpg
768 ms
escut.png;jsessionid=476B98C041B87DF9350741D92520C07A
116 ms
978899;jsessionid=476B98C041B87DF9350741D92520C07A
162 ms
978902;jsessionid=476B98C041B87DF9350741D92520C07A
257 ms
978903;jsessionid=476B98C041B87DF9350741D92520C07A
301 ms
1035235;jsessionid=476B98C041B87DF9350741D92520C07A
330 ms
6e0bba89-7959-44df-9668-6117ce985fd0
1372 ms
widget_unfold_b.png;jsessionid=476B98C041B87DF9350741D92520C07A
422 ms
ccfcc7d7-fd7e-4238-9027-c9a18ae7a2c2
553 ms
dc740957-0e45-49ff-8a6c-1c834e18c022
688 ms
c54907a8-dc54-4bbf-aa96-2f0dc41d924a
696 ms
980d0fd1-50e6-4d03-bd21-a963c82b8881
857 ms
05deec95-9567-405c-9a4e-6f3c22874ef9
998 ms
9570fdca-8f31-4c7e-8065-1fdddeb99224
1134 ms
widget_fold_w.png;jsessionid=476B98C041B87DF9350741D92520C07A
809 ms
widget_unfold_w.png;jsessionid=476B98C041B87DF9350741D92520C07A
875 ms
78946955-c1c0-482b-94c1-459c9c630d00
925 ms
e34f1789-3f07-4587-834c-23c385aea5f4
968 ms
6dfa96e5-21ca-4057-a736-34ad273449de
988 ms
b5cd11ba-bf7c-4ade-96a5-bfb0f28ae727
1036 ms
798b7790-2ebe-432a-b880-97b3b6b91774
1081 ms
rss_b.png;jsessionid=476B98C041B87DF9350741D92520C07A
1099 ms
widget_close_b.png;jsessionid=476B98C041B87DF9350741D92520C07A
1108 ms
4679257a-caa3-4915-b4df-5694af63aa76
1149 ms
facebook_b.png;jsessionid=476B98C041B87DF9350741D92520C07A
1192 ms
twitter_b.png;jsessionid=476B98C041B87DF9350741D92520C07A
1211 ms
blogger_b.png;jsessionid=476B98C041B87DF9350741D92520C07A
1218 ms
youtube_b.png;jsessionid=476B98C041B87DF9350741D92520C07A
1241 ms
flickr_b.png;jsessionid=476B98C041B87DF9350741D92520C07A
1259 ms
1197054;jsessionid=476B98C041B87DF9350741D92520C07A
1337 ms
1345442;jsessionid=476B98C041B87DF9350741D92520C07A
1349 ms
1111517
1366 ms
10394503_1167609296592242_5128813417010083712_n.jpg
127 ms
clock
1344 ms
1111489
1408 ms
1102674
1435 ms
1480859
1314 ms
1083594
1246 ms
1040261
1219 ms
1040188
1189 ms
1082679
1871 ms
1042391
1265 ms
helvetica.woff
2082 ms
helvetica-bold.woff
1634 ms
1082676
983 ms
1041327
1037 ms
1041445
1342 ms
1083595
999 ms
1041455
1018 ms
1040270
1073 ms
1040250
1084 ms
1040288
1119 ms
1101385
1158 ms
lupa.png
1214 ms
carousel_left.png
1176 ms
carousel_right.png
1178 ms
1012811
1217 ms
96e3d6dc-b209-41a9-b9d2-a3d1b020aa0f
3876 ms
47a6d070-c66f-4afa-b28a-4cdffc1fac64
3798 ms
34601eb4-9d58-4170-99d3-c38e06a9dc27
1629 ms
f5eee59a-dfa9-42a4-92b8-9e3f308eec70
1847 ms
1012942
1397 ms
1050270
1425 ms
1089115
1734 ms
1606900
1635 ms
1041808
1817 ms
1101546
1798 ms
1601692
1898 ms
1040462
1952 ms
widget_selector_left_off.png
1897 ms
widget_selector_right_on.png
1778 ms
1238794
2573 ms
1101382
2014 ms
list_icon.png
1871 ms
santfeliu.cat 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-hidden="true"] elements contain focusable descendents
santfeliu.cat 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
santfeliu.cat 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
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 Santfeliu.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 Santfeliu.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.
santfeliu.cat
Open Graph description is not detected on the main page of Sant Feliu. 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: