5.4 sec in total
335 ms
4.5 sec
518 ms
Welcome to api.cat homepage info - get ready to check API best content for Spain right away, or after learning these important things about api.cat
Venda i lloguer de cases i pisos en exclusiva a Catalunya. Compra pisos, cases, obra nova, pisos de bancs al portal dels professionals immobiliaris.
Visit api.catWe analyzed Api.cat page load time and found that the first response time was 335 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
api.cat performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value9.6 s
0/100
25%
Value9.5 s
11/100
10%
Value570 ms
52/100
30%
Value0
100/100
15%
Value12.2 s
15/100
10%
335 ms
2556 ms
201 ms
221 ms
221 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 46% of them (33 requests) were addressed to the original Api.cat, 7% (5 requests) were made to Pagead2.googlesyndication.com and 6% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Api.cat.
Page size can be reduced by 1.0 MB (52%)
2.0 MB
963.5 kB
In fact, the total size of Api.cat main page is 2.0 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. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 79.3 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 79.3 kB or 85% of the original size.
Potential reduce by 14.4 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. API images are well optimized though.
Potential reduce by 787.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 787.6 kB or 71% of the original size.
Potential reduce by 148.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. Api.cat needs all CSS files to be minified and compressed as it can save up to 148.8 kB or 81% of the original size.
Number of requests can be reduced by 32 (48%)
67
35
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of API. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
api.cat
335 ms
www.api.cat
2556 ms
bootstrap.min.css
201 ms
full-slider.css
221 ms
font-awesome.min.css
221 ms
my_style.min.css
216 ms
jquery-1.9.1.js
684 ms
jquery-ui-1.10.2.custom.min.js
706 ms
bootstrap.js
392 ms
jfunctions_g.js
296 ms
js
80 ms
maps.google.polygon.containsLatLng.js
296 ms
maps.google.apicat.searchmap.js
392 ms
conversion.js
22 ms
adsbygoogle.js
5 ms
gtm.js
109 ms
57 ms
adinton.php
420 ms
cat.png
190 ms
es.png
194 ms
en.png
194 ms
ru.png
190 ms
fra.png
189 ms
ger.png
192 ms
chi.png
290 ms
arb.png
288 ms
common.js
78 ms
util.js
82 ms
geocoder.js
81 ms
glyphicons-halflings-regular.woff
273 ms
1.jpg
394 ms
logo.png
280 ms
mobile_2.jpg
281 ms
home_banner_credit_api.jpg
392 ms
196Tecnitasa_v2.gif
468 ms
7689emsos.gif
389 ms
4009Banner-AURUM-v2.gif
666 ms
1546BannerOfertaColectivos_Pro_350071_260x217_cat.gif
391 ms
1526Mutua-de-Propietarios-banner-260-x--217_2.jpg
476 ms
1481Marsh-banner-260-x-108-px.gif
484 ms
facebook_banner.png
485 ms
twitter_banner.png
486 ms
foto_1.jpg
917 ms
foto_1.jpg
695 ms
foto_1.jpg
694 ms
foto_1.jpg
791 ms
205 ms
foto_1.jpg
785 ms
foto_1.jpg
688 ms
foto_1.jpg
689 ms
foto_1.jpg
785 ms
foto_1.jpg
687 ms
foto_1.jpg
687 ms
foto_1.jpg
880 ms
foto_1.jpg
784 ms
ca-pub-6286723423362201.js
175 ms
zrt_lookup.html
100 ms
show_ads_impl.js
109 ms
analytics.js
84 ms
ads
315 ms
osd.js
13 ms
collect
11 ms
collect
67 ms
adnTracker.php
235 ms
11204545574924786011
34 ms
abg.js
38 ms
m_js_controller.js
52 ms
googlelogo_color_112x36dp.png
86 ms
s
3 ms
x_button_blue2.png
5 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
3 ms
api.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
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.
api.cat best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
api.cat SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a valid hreflang
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 Api.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 Api.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.
api.cat
Open Graph description is not detected on the main page of API. 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: