Tools & Wizards About Us
san-fernando.aquopolis.es screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

san-fernando.aquopolis.es

Welcome!

Page Load Speed

3.6 sec in total

First Response

363 ms

Resources Loaded

2.7 sec

Page Rendered

468 ms

san-fernando.aquopolis.es screenshot

About Website

Welcome to san-fernando.aquopolis.es homepage info - get ready to check San Fernando Aquopolis best content for Spain right away, or after learning these important things about san-fernando.aquopolis.es

Ven a Aquopolis San Fernando, disfruta de las mejores atracciones acuáticas en familia y relájate en nuestra Zona Vip a 10 minutos de Madrid. ¡Te esperamos!

Visit san-fernando.aquopolis.es

Key Findings

We analyzed San-fernando.aquopolis.es page load time and found that the first response time was 363 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

san-fernando.aquopolis.es performance score

0

Network Requests Diagram

san-fernando.aquopolis.es

363 ms

css

26 ms

language-selector.css

77 ms

jquery.fancybox-1.3.4.css

153 ms

layerslider.css

154 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 92% of them (110 requests) were addressed to the original San-fernando.aquopolis.es, 3% (3 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (657 ms) belongs to the original domain San-fernando.aquopolis.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (52%)

Content Size

3.6 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of San-fernando.aquopolis.es main page is 3.6 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. 70% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 50.8 kB

  • Original 61.3 kB
  • After minification 57.4 kB
  • After compression 10.6 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 50.8 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 51.8 kB

  • Original 1.2 MB
  • After minification 1.2 MB

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. San Fernando Aquopolis images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 723.4 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 381.7 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 723.4 kB or 65% of the original size.

CSS Optimization

-86%

Potential reduce by 1.0 MB

  • Original 1.2 MB
  • After minification 984.5 kB
  • After compression 164.7 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. San-fernando.aquopolis.es needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 88 (75%)

Requests Now

117

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of San Fernando Aquopolis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 61 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

san-fernando.aquopolis.es

san-fernando.aquopolis.es

363 ms

css

css

26 ms

language-selector.css

language-selector.css

77 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

153 ms

layerslider.css

layerslider.css

154 ms

css

css

50 ms

cli-style.css

cli-style.css

182 ms

basic.css

basic.css

184 ms

custom.css

custom.css

179 ms

tooltipster.css

tooltipster.css

177 ms

js_composer_front.css

js_composer_front.css

300 ms

style.css

style.css

312 ms

dyncss.php

dyncss.php

251 ms

css

css

64 ms

print.css

print.css

251 ms

frontend.min.css

frontend.min.css

409 ms

last_minute_fixes.css

last_minute_fixes.css

262 ms

jquery.js

jquery.js

400 ms

jquery-migrate.min.js

jquery-migrate.min.js

327 ms

jquery.fancybox-1.3.4.js

jquery.fancybox-1.3.4.js

343 ms

hammer.min.js

hammer.min.js

373 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

373 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

476 ms

greensock.js

greensock.js

501 ms

layerslider.transitions.js

layerslider.transitions.js

448 ms

cookielawinfo.js

cookielawinfo.js

446 ms

jquery.tooltipster.min.js

jquery.tooltipster.min.js

472 ms

bootstrap.min.js

bootstrap.min.js

481 ms

bootstrap-select.js

bootstrap-select.js

520 ms

core.min.js

core.min.js

521 ms

widget.min.js

widget.min.js

546 ms

accordion.min.js

accordion.min.js

550 ms

mouse.min.js

mouse.min.js

557 ms

slider.min.js

slider.min.js

580 ms

resizable.min.js

resizable.min.js

595 ms

draggable.min.js

draggable.min.js

596 ms

button.min.js

button.min.js

623 ms

position.min.js

position.min.js

626 ms

dialog.min.js

dialog.min.js

637 ms

js

js

120 ms

map.css

map.css

657 ms

ticketstyle.css

ticketstyle.css

585 ms

tabs.min.js

tabs.min.js

536 ms

sortable.min.js

sortable.min.js

560 ms

droppable.min.js

droppable.min.js

538 ms

datepicker.min.js

datepicker.min.js

547 ms

menu.min.js

menu.min.js

572 ms

autocomplete.min.js

autocomplete.min.js

573 ms

frontend.min.js

frontend.min.js

610 ms

map-instance.js

map-instance.js

527 ms

hoverIntent.min.js

hoverIntent.min.js

495 ms

style.css

style.css

519 ms

ubermenu.min.js

ubermenu.min.js

503 ms

custom.js

custom.js

496 ms

comment-reply.min.js

comment-reply.min.js

492 ms

custom-script.js

custom-script.js

505 ms

sitepress.js

sitepress.js

507 ms

js_composer_front.js

js_composer_front.js

476 ms

count.js

count.js

461 ms

nav-resp.js

nav-resp.js

488 ms

doubletaptogo.js

doubletaptogo.js

468 ms

bootstrap-alert.js

bootstrap-alert.js

480 ms

bootstrap-dropdown.js

bootstrap-dropdown.js

495 ms

jquery.sticky.js

jquery.sticky.js

483 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

470 ms

jquery.easy-pie-chart.js

jquery.easy-pie-chart.js

491 ms

bootstrap-tab.js

bootstrap-tab.js

474 ms

bootstrap-tooltip.js

bootstrap-tooltip.js

483 ms

isotope.js

isotope.js

494 ms

isotope-custom.js

isotope-custom.js

477 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

476 ms

masonry.min.js

masonry.min.js

491 ms

jquery.visible.min.js

jquery.visible.min.js

472 ms

jquery.fitvids.js

jquery.fitvids.js

484 ms

mexin-custom.js

mexin-custom.js

489 ms

iframeResizer.min.js

iframeResizer.min.js

474 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

482 ms

color-skins.css

color-skins.css

337 ms

base.css

base.css

347 ms

skeleton.css

skeleton.css

363 ms

prettyPhoto.css

prettyPhoto.css

377 ms

slide1.css

slide1.css

382 ms

flexslider.css

flexslider.css

406 ms

blox.css

blox.css

412 ms

iconfonts.css

iconfonts.css

423 ms

widgets.css

widgets.css

440 ms

analytics.js

analytics.js

21 ms

ts.js

ts.js

309 ms

collect

collect

12 ms

tsr.js

tsr.js

138 ms

san-fernando.aquopolis.es

san-fernando.aquopolis.es

115 ms

bg.jpg

bg.jpg

533 ms

logo.png

logo.png

242 ms

ico-search.png

ico-search.png

109 ms

logo_mov.png

logo_mov.png

184 ms

ico_settings.jpg

ico_settings.jpg

107 ms

ico-search2.png

ico-search2.png

181 ms

ico_youtube.png

ico_youtube.png

182 ms

btn_yellowsmall.png

btn_yellowsmall.png

182 ms

bg_nav.png

bg_nav.png

220 ms

tickets.png

tickets.png

386 ms

blank.gif

blank.gif

238 ms

menu.png

menu.png

249 ms

Home_Atracciones.jpg

Home_Atracciones.jpg

523 ms

Home_Como-llegar.jpg

Home_Como-llegar.jpg

555 ms

Home_Donde-Comer.jpg

Home_Donde-Comer.jpg

397 ms

home_zona_vip.jpg

home_zona_vip.jpg

408 ms

home_pase_anual.jpg

home_pase_anual.jpg

463 ms

logo_parques.jpg

logo_parques.jpg

479 ms

footer_waves.png

footer_waves.png

570 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

532 ms

label.png

label.png

546 ms

onda.png

onda.png

584 ms

bg_topwaves.svg

bg_topwaves.svg

591 ms

btn_feedback.png

btn_feedback.png

606 ms

overlay.png

overlay.png

594 ms

count.js

count.js

50 ms

skin.css

skin.css

486 ms

li_submenu.png

li_submenu.png

482 ms

SEO Factors

san-fernando.aquopolis.es SEO score

0

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise San-fernando.aquopolis.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that San-fernando.aquopolis.es 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.

Social Sharing Optimization

san-fernando.aquopolis.es

Open Graph data is detected on the main page of San Fernando Aquopolis. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: