Tools & Wizards About Us
525.es screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

525.es

Hotel 525 | Los Alcázares | Murcia | Official Website

Page Load Speed

3.2 sec in total

First Response

299 ms

Resources Loaded

1.5 sec

Page Rendered

1.4 sec

525.es screenshot

About Website

Welcome to 525.es homepage info - get ready to check 525 best content right away, or after learning these important things about 525.es

Come enjoy a warm and welcoming stay in our spacious rooms with designer furniture to make your time in Los Alcázares an unforgettable experience.

Visit 525.es

Key Findings

We analyzed 525.es page load time and found that the first response time was 299 ms and then it took 2.9 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

525.es performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value4,640 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.115

86/100

15%

TTI (Time to Interactive)

Value30.4 s

0/100

10%

Network Requests Diagram

525.es

299 ms

19 ms

styles.css

158 ms

whatsappme.min.css

157 ms

flickity.min.css

158 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 48% of them (34 requests) were addressed to the original 525.es, 21% (15 requests) were made to Cdnwp1.mirai.com and 11% (8 requests) were made to Cdnwp0.mirai.com. The less responsive or slowest element that took the longest time to load (592 ms) belongs to the original domain 525.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.8 kB (3%)

Content Size

3.3 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 525.es main page is 3.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 64.9 kB

  • Original 82.9 kB
  • After minification 76.3 kB
  • After compression 18.0 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 64.9 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 1.5 kB

  • Original 2.9 MB
  • After minification 2.9 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. 525 images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 7.4 kB

  • Original 317.2 kB
  • After minification 317.0 kB
  • After compression 309.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-15%

Potential reduce by 11.0 kB

  • Original 72.1 kB
  • After minification 72.1 kB
  • After compression 61.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. 525.es needs all CSS files to be minified and compressed as it can save up to 11.0 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (44%)

Requests Now

59

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

525.es

525.es

299 ms

19 ms

styles.css

styles.css

158 ms

whatsappme.min.css

whatsappme.min.css

157 ms

flickity.min.css

flickity.min.css

158 ms

bootstrap.css

bootstrap.css

147 ms

bootstrap-addons.css

bootstrap-addons.css

144 ms

css

css

176 ms

mirai-icofonts.css

mirai-icofonts.css

144 ms

skeleton.css

skeleton.css

160 ms

style.css

style.css

80 ms

gdpr_cc_addon.css

gdpr_cc_addon.css

166 ms

gdpr-main.css

gdpr-main.css

162 ms

engine.css

engine.css

131 ms

jquery.min.js

jquery.min.js

169 ms

scripts.js

scripts.js

156 ms

mirai.common.js

mirai.common.js

156 ms

bootstrap.min.js

bootstrap.min.js

163 ms

back-to-top.js

back-to-top.js

164 ms

whatsappme.min.js

whatsappme.min.js

165 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

165 ms

fixes.js

fixes.js

162 ms

gdpr_cc_addon.js

gdpr_cc_addon.js

169 ms

main.js

main.js

166 ms

mirai.loader.js

mirai.loader.js

164 ms

api.js

api.js

171 ms

custom.1601983535.js

custom.1601983535.js

168 ms

css

css

30 ms

logo-5d6a15f718.svg

logo-5d6a15f718.svg

271 ms

footer-logo-94f9c23517.png

footer-logo-94f9c23517.png

241 ms

background.webp

background.webp

238 ms

logo-apartamentos-525.png

logo-apartamentos-525.png

368 ms

logo-525tours.svg

logo-525tours.svg

368 ms

sydney-opera-house.svg

sydney-opera-house.svg

381 ms

logo.png

logo.png

383 ms

home-header.jpg

home-header.jpg

421 ms

HOME_02_HOTEL.jpg

HOME_02_HOTEL.jpg

414 ms

home-apart.jpg

home-apart.jpg

420 ms

Imagen9.jpg

Imagen9.jpg

414 ms

pool.jpg

pool.jpg

450 ms

room-home.jpg

room-home.jpg

450 ms

HOME_06_CELEBRACIONES.jpg

HOME_06_CELEBRACIONES.jpg

422 ms

HOME_06_SALONES.jpg

HOME_06_SALONES.jpg

421 ms

HOME_07_GASTRONOPMIA_BAR_ROJO.jpg

HOME_07_GASTRONOPMIA_BAR_ROJO.jpg

454 ms

HOME_07_GASTRONOPMIA_AZOTEA.jpg

HOME_07_GASTRONOPMIA_AZOTEA.jpg

499 ms

home-amazonia.jpg

home-amazonia.jpg

453 ms

HOME_08_BIENESTAR.jpg

HOME_08_BIENESTAR.jpg

454 ms

transfer.jpg

transfer.jpg

458 ms

HOME_08_BIKE.jpg

HOME_08_BIKE.jpg

458 ms

HOME_09_GYM.jpg

HOME_09_GYM.jpg

502 ms

HOME_09_525_TOURS.jpg

HOME_09_525_TOURS.jpg

501 ms

goplf1.jpg

goplf1.jpg

502 ms

HOME_09_PARKING.jpg

HOME_09_PARKING.jpg

573 ms

525-Mapa-actualizado-Agosto-2022.jpg

525-Mapa-actualizado-Agosto-2022.jpg

579 ms

Union-Europea.svg

Union-Europea.svg

575 ms

escudo_MURCIA-1280x624.svg

escudo_MURCIA-1280x624.svg

592 ms

osga.svg

osga.svg

583 ms

infomurcia.svg

infomurcia.svg

580 ms

desinfeccion.png

desinfeccion.png

592 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

449 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

456 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

570 ms

mirai-icofonts.ttf

mirai-icofonts.ttf

202 ms

t5t9IRIUKY-TFF_LW5lnMR3v2DnvYtiWfT8b.ttf

t5t9IRIUKY-TFF_LW5lnMR3v2DnvYtiWfT8b.ttf

356 ms

t5t9IRIUKY-TFF_LW5lnMR3v2DnvPNiWfT8b.ttf

t5t9IRIUKY-TFF_LW5lnMR3v2DnvPNiWfT8b.ttf

357 ms

t5t9IRIUKY-TFF_LW5lnMR3v2DnvvN-WfT8b.ttf

t5t9IRIUKY-TFF_LW5lnMR3v2DnvvN-WfT8b.ttf

356 ms

recaptcha__en.js

recaptcha__en.js

265 ms

lity.js

lity.js

341 ms

ajax-loader.gif

ajax-loader.gif

111 ms

nunito-v8-latin-regular.woff

nunito-v8-latin-regular.woff

19 ms

nunito-v8-latin-700.woff

nunito-v8-latin-700.woff

19 ms

Accessibility Review

525.es accessibility score

73

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

525.es best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

525.es SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

525.es

Open Graph description is not detected on the main page of 525. 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: