4.6 sec in total
397 ms
4 sec
138 ms
Welcome to float-in.pt homepage info - get ready to check Float In best content for Portugal right away, or after learning these important things about float-in.pt
Relaxe com os melhores momentos spa. Descubra a Massagem e o Tratamento perfeito para o seu corpo e mente. 3 spas em Lisboa, disponíveis 7 dias p/semana
Visit float-in.ptWe analyzed Float-in.pt page load time and found that the first response time was 397 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
float-in.pt performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value12.3 s
0/100
25%
Value11.6 s
4/100
10%
Value3,660 ms
1/100
30%
Value0.001
100/100
15%
Value13.9 s
10/100
10%
397 ms
1581 ms
13 ms
222 ms
254 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 87% of them (55 requests) were addressed to the original Float-in.pt, 3% (2 requests) were made to Stats.g.doubleclick.net and 3% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Float-in.pt.
Page size can be reduced by 67.4 kB (12%)
575.7 kB
508.3 kB
In fact, the total size of Float-in.pt main page is 575.7 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. 40% of websites need less resources to load. Images take 497.9 kB which makes up the majority of the site volume.
Potential reduce by 27.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 27.4 kB or 80% of the original size.
Potential reduce by 23.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. Float In images are well optimized though.
Potential reduce by 16.2 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 16.2 kB or 38% of the original size.
Potential reduce by 941 B
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. Float-in.pt needs all CSS files to be minified and compressed as it can save up to 941 B or 79% of the original size.
Number of requests can be reduced by 31 (53%)
59
28
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Float In. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
float-in.pt
397 ms
www.float-in.pt
1581 ms
jcemediabox.css
13 ms
style.css
222 ms
widgetkit-779efcd3-e63e2549.css
254 ms
bootstrap-1e2c9c57.css
679 ms
template.css
13 ms
mod_accordeonck_css.php
300 ms
style.css
13 ms
jcemediabox.js
243 ms
jquery.min-373987a2.js
18 ms
jquery-noconflict-30f7062b.js
21 ms
jquery-migrate.min-3a7716f7.js
24 ms
widgetkit-1fe080fc-4290cfde.js
375 ms
jquery.ui.core.min.js
446 ms
mod_accordeonck.js
469 ms
jquery.easing.1.3.js
250 ms
default.js
252 ms
template-936431c1.css
777 ms
template-ddc1518e.js
296 ms
spotlight.js
6 ms
www.float-in.pt
87 ms
logo.png
14 ms
pt.gif
15 ms
en.gif
15 ms
menu-massagens.jpg
15 ms
menu-flutuacao.jpg
291 ms
menu-programas.jpg
223 ms
menu-a-dois.jpg
241 ms
menu-promocoes.jpg
256 ms
menu-vouchers.jpg
410 ms
menu-rapido.jpg
244 ms
menu-contactos.jpg
451 ms
social-facebook.png
242 ms
social-twitter.png
244 ms
social-google-rato.png
246 ms
social-google-picoas.png
245 ms
social-pinterest.png
247 ms
social-instagram.png
248 ms
social-blogger.png
249 ms
social-tripadvisor-excellence.png
249 ms
menu_line_item.png
250 ms
64c15b659fbc476dd9f91b510f128a05.jpg
252 ms
55008b09d7d80ba14e135c293bfcf3dd.jpg
941 ms
ed72ffbecc37e344a9fdd8df63534f90.jpg
825 ms
67c7e427ee67ed4c95441ecd06568845.jpg
991 ms
fbds.js
136 ms
Roboto-Light-webfont.woff
517 ms
Roboto-Thin-webfont.woff
764 ms
dc.js
52 ms
iframe_api
41 ms
popup.html
603 ms
tooltip.html
696 ms
loading.gif
841 ms
play.png
944 ms
pause.png
970 ms
next.png
990 ms
back.png
1081 ms
__utm.gif
11 ms
www-widgetapi.js
5 ms
103 ms
justify-bg.png
220 ms
21 ms
float-in.pt 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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
float-in.pt 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
float-in.pt 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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Float-in.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Float-in.pt 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.
float-in.pt
Open Graph data is detected on the main page of Float In. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: