8.1 sec in total
394 ms
7.1 sec
629 ms
Visit sentosa.pl now to see the best up-to-date Sentosa content and also check out these interesting facts you probably never knew about sentosa.pl
Sprawdź
Visit sentosa.plWe analyzed Sentosa.pl page load time and found that the first response time was 394 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
sentosa.pl performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value9.2 s
1/100
25%
Value9.6 s
11/100
10%
Value2,170 ms
6/100
30%
Value0
100/100
15%
Value13.5 s
11/100
10%
394 ms
4239 ms
67 ms
123 ms
239 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 49% of them (38 requests) were addressed to the original Sentosa.pl, 18% (14 requests) were made to Maps.google.com and 10% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Sentosa.pl.
Page size can be reduced by 900.4 kB (43%)
2.1 MB
1.2 MB
In fact, the total size of Sentosa.pl main page is 2.1 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. 65% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 76.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 76.4 kB or 84% 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. Sentosa images are well optimized though.
Potential reduce by 738.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 738.5 kB or 62% of the original size.
Potential reduce by 62.4 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. Sentosa.pl needs all CSS files to be minified and compressed as it can save up to 62.4 kB or 82% of the original size.
Number of requests can be reduced by 26 (38%)
69
43
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sentosa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
sentosa.pl
394 ms
www.sentosa.pl
4239 ms
css
67 ms
style.css
123 ms
jquery.fancybox.css
239 ms
js
27 ms
libs.min.js
842 ms
gmaps.min.js
287 ms
functions.src.min.js
287 ms
sdk.js
229 ms
ga.js
216 ms
logo.png
226 ms
common.js
30 ms
map.js
31 ms
util.js
28 ms
marker.js
27 ms
sentopark.jpg
384 ms
atrium-park.jpg
385 ms
top-slide-1.jpg
383 ms
ico-view.png
202 ms
bg-pig.jpg
200 ms
ico-view-black.png
382 ms
top-slide-2.jpg
565 ms
small_investition-box-bg.jpg
382 ms
top-slide-3.jpg
837 ms
small_zarabiaj-inewstujac.jpg
496 ms
ico-mouse.png
466 ms
sento-pink.png
494 ms
ico-flag.png
503 ms
ico-home.png
587 ms
ico-realizations.png
621 ms
ico-pencil.png
629 ms
sento-more-img.jpg
748 ms
atrium-more-img.jpg
683 ms
checkbox-checked.png
704 ms
checkbox.png
773 ms
select-ico.png
772 ms
ico-flag-white.png
808 ms
sento-logo-white.png
824 ms
ico-star-white.png
864 ms
must-know-bg.jpg
894 ms
home-key-bg.jpg
1245 ms
fast-contact-ico.png
925 ms
nomonday.png
953 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
122 ms
BTu4SsVveqk58cdYjlaM9g.ttf
182 ms
zpv3sOKAbMf4wff105oLjw.ttf
189 ms
__utm.gif
103 ms
onion.js
56 ms
openhand_8_8.cur
114 ms
310 ms
ViewportInfoService.GetViewportInfo
75 ms
stats.js
69 ms
controls.js
70 ms
xd_arbiter.php
228 ms
xd_arbiter.php
272 ms
transparent.png
132 ms
css
101 ms
sento-marker.png
645 ms
atrium-marker.png
675 ms
vt
85 ms
vt
85 ms
vt
77 ms
vt
76 ms
vt
73 ms
vt
77 ms
vt
87 ms
google4.png
52 ms
mapcnt6.png
53 ms
sv5.png
53 ms
tmapctrl.png
44 ms
tmapctrl4.png
39 ms
google_white5.png
42 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
7 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
7 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
22 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
22 ms
AuthenticationService.Authenticate
143 ms
sentosa.pl 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.
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.
sentosa.pl 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
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
sentosa.pl 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 doesn't use legible font sizes
Tap targets are not sized appropriately
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sentosa.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Sentosa.pl 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.
sentosa.pl
Open Graph description is not detected on the main page of Sentosa. 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: