Tools & Wizards About Us
ftorres.es screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

ftorres.es

Mis notas imperdibles ... - sobre programación php/mysql, python, jquery, css, js, herramientas de desarrollo, comercio electrónico y experimentos con...

Page Load Speed

5.6 sec in total

First Response

926 ms

Resources Loaded

4.1 sec

Page Rendered

598 ms

ftorres.es screenshot

About Website

Visit ftorres.es now to see the best up-to-date Ftorres content and also check out these interesting facts you probably never knew about ftorres.es

sobre programación php/mysql, python, jquery, css, js, herramientas de desarrollo, comercio electrónico y experimentos con arduino.

Visit ftorres.es

Key Findings

We analyzed Ftorres.es page load time and found that the first response time was 926 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

ftorres.es performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value670 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.125

83/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

www.ftorres.es

926 ms

style.min.css

96 ms

style.min.css

185 ms

style.min.css

342 ms

style.min.css

254 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 90% of them (92 requests) were addressed to the original Ftorres.es, 5% (5 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Rcm-eu.amazon-adsystem.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Ftorres.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 238.2 kB (8%)

Content Size

2.8 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ftorres.es main page is 2.8 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. 60% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 143.3 kB

  • Original 180.2 kB
  • After minification 167.2 kB
  • After compression 36.9 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 143.3 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 88.9 kB

  • Original 1.6 MB
  • After minification 1.5 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. Ftorres images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.5 kB

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

CSS Optimization

-3%

Potential reduce by 3.6 kB

  • Original 107.3 kB
  • After minification 107.3 kB
  • After compression 103.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. Ftorres.es has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 76 (84%)

Requests Now

91

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.ftorres.es

www.ftorres.es

926 ms

style.min.css

style.min.css

96 ms

style.min.css

style.min.css

185 ms

style.min.css

style.min.css

342 ms

style.min.css

style.min.css

254 ms

style.min.css

style.min.css

272 ms

style.min.css

style.min.css

298 ms

blocks.style.build.css

blocks.style.build.css

297 ms

style.min.css

style.min.css

398 ms

bootstrap.min.css

bootstrap.min.css

432 ms

font-awesome.css

font-awesome.css

361 ms

css

css

33 ms

owl.carousel.min.css

owl.carousel.min.css

401 ms

style.css

style.css

501 ms

enlighterjs.min.css

enlighterjs.min.css

438 ms

jquery.min.js

jquery.min.js

458 ms

jquery-migrate.min.js

jquery-migrate.min.js

501 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

608 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

608 ms

wp-polyfill.min.js

wp-polyfill.min.js

610 ms

react.min.js

react.min.js

612 ms

autop.min.js

autop.min.js

613 ms

blob.min.js

blob.min.js

615 ms

block-serialization-default-parser.min.js

block-serialization-default-parser.min.js

613 ms

hooks.min.js

hooks.min.js

614 ms

deprecated.min.js

deprecated.min.js

616 ms

dom.min.js

dom.min.js

644 ms

react-dom.min.js

react-dom.min.js

817 ms

escape-html.min.js

escape-html.min.js

708 ms

element.min.js

element.min.js

712 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

700 ms

i18n.min.js

i18n.min.js

701 ms

keycodes.min.js

keycodes.min.js

720 ms

priority-queue.min.js

priority-queue.min.js

783 ms

compose.min.js

compose.min.js

791 ms

private-apis.min.js

private-apis.min.js

809 ms

redux-routine.min.js

redux-routine.min.js

813 ms

data.min.js

data.min.js

810 ms

html-entities.min.js

html-entities.min.js

779 ms

dom-ready.min.js

dom-ready.min.js

699 ms

a11y.min.js

a11y.min.js

665 ms

rich-text.min.js

rich-text.min.js

640 ms

shortcode.min.js

shortcode.min.js

624 ms

blocks.min.js

blocks.min.js

645 ms

url.min.js

url.min.js

621 ms

api-fetch.min.js

api-fetch.min.js

608 ms

moment.min.js

moment.min.js

599 ms

date.min.js

date.min.js

820 ms

primitives.min.js

primitives.min.js

586 ms

warning.min.js

warning.min.js

603 ms

components.min.js

components.min.js

856 ms

keyboard-shortcuts.min.js

keyboard-shortcuts.min.js

556 ms

cm

cm

70 ms

cm

cm

64 ms

commands.min.js

commands.min.js

484 ms

notices.min.js

notices.min.js

515 ms

preferences-persistence.min.js

preferences-persistence.min.js

534 ms

preferences.min.js

preferences.min.js

532 ms

style-engine.min.js

style-engine.min.js

565 ms

token-list.min.js

token-list.min.js

614 ms

wordcount.min.js

wordcount.min.js

616 ms

block-editor.min.js

block-editor.min.js

939 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

16 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

28 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

50 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

64 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

63 ms

core-data.min.js

core-data.min.js

653 ms

media-utils.min.js

media-utils.min.js

707 ms

patterns.min.js

patterns.min.js

665 ms

server-side-render.min.js

server-side-render.min.js

620 ms

editor.min.js

editor.min.js

754 ms

blocks.build.js

blocks.build.js

710 ms

popper.min.js

popper.min.js

697 ms

bootstrap.min.js

bootstrap.min.js

707 ms

owl.carousel.min.js

owl.carousel.min.js

652 ms

owl.carousel-settings.js

owl.carousel-settings.js

706 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

698 ms

jquery.matchHeight-settings.js

jquery.matchHeight-settings.js

717 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

724 ms

jquery.marquee.min.js

jquery.marquee.min.js

721 ms

jquery.marquee-settings.js

jquery.marquee-settings.js

789 ms

jquery.sticky.js

jquery.sticky.js

802 ms

jquery.sticky-settings.js

jquery.sticky-settings.js

776 ms

scripts.js

scripts.js

769 ms

enlighterjs.min.js

enlighterjs.min.js

764 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

743 ms

cabecera.jpg

cabecera.jpg

1118 ms

attachment_white.png

attachment_white.png

767 ms

cabecera-python-juego-vida.jpg

cabecera-python-juego-vida.jpg

927 ms

cabecera-python-configuracion.png

cabecera-python-configuracion.png

786 ms

cabecera-symfony_workflows.png

cabecera-symfony_workflows.png

700 ms

cabecera-symfony_fixtures.png

cabecera-symfony_fixtures.png

705 ms

cabecera-shopify.png

cabecera-shopify.png

679 ms

cabecera-mysql.png

cabecera-mysql.png

911 ms

25-a%C3%B1os-de-php.jpg

25-a%C3%B1os-de-php.jpg

718 ms

cabecera-arduin-sensor-ultrasonido.jpg

cabecera-arduin-sensor-ultrasonido.jpg

712 ms

cabecera-git-comandos.png

cabecera-git-comandos.png

717 ms

cabecera-php-errores.png

cabecera-php-errores.png

723 ms

notas-imperdibles-1.jpg

notas-imperdibles-1.jpg

736 ms

cm

cm

7 ms

cm

cm

7 ms

Accessibility Review

ftorres.es accessibility score

85

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

<frame> or <iframe> elements do not have a title

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

Heading elements are not in a sequentially-descending order

Best Practices

ftorres.es best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

ftorres.es SEO score

98

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 Ftorres.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 Ftorres.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

ftorres.es

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