5.6 sec in total
249 ms
5.2 sec
203 ms
Visit frami.es now to see the best up-to-date Frami content and also check out these interesting facts you probably never knew about frami.es
Venta de maquinaria de hostelería, productos como cocinas industriales, lavandería, alimentación, Servicio técnico en Benidorm y toda la provincia Alicante
Visit frami.esWe analyzed Frami.es page load time and found that the first response time was 249 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
frami.es performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value6.6 s
8/100
25%
Value11.0 s
6/100
10%
Value300 ms
78/100
30%
Value0.003
100/100
15%
Value15.1 s
7/100
10%
249 ms
2450 ms
307 ms
311 ms
308 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Frami.es, 85% (85 requests) were made to Framimaquinariadehosteleria.es and 9% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Framimaquinariadehosteleria.es.
Page size can be reduced by 263.3 kB (13%)
2.1 MB
1.8 MB
In fact, the total size of Frami.es 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. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 223.8 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 223.8 kB or 88% of the original size.
Potential reduce by 29.9 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. Frami images are well optimized though.
Potential reduce by 531 B
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.
Potential reduce by 9.0 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. Frami.es has all CSS files already compressed.
Number of requests can be reduced by 63 (76%)
83
20
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frami. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
frami.es
249 ms
framimaquinariadehosteleria.es
2450 ms
main.css
307 ms
frontend.css
311 ms
trp-language-switcher.css
308 ms
header-footer-elementor.css
314 ms
elementor-icons.min.css
346 ms
frontend-lite.min.css
523 ms
swiper.min.css
422 ms
post-571.css
423 ms
frontend-lite.min.css
424 ms
global.css
457 ms
post-4427.css
526 ms
fonts.min.css
529 ms
css
32 ms
style.css
741 ms
style.css
567 ms
style-elementor.css
636 ms
style-crazy-load.css
633 ms
style-large.css
637 ms
style-font-weight-500.css
683 ms
nasa-sc-woo.css
762 ms
nasa-sc.css
764 ms
dynamic.css
755 ms
css
46 ms
fontawesome.min.css
794 ms
solid.min.css
841 ms
jquery.min.js
850 ms
jquery-migrate.min.js
868 ms
jquery.blockUI.min.js
865 ms
add-to-cart.min.js
907 ms
js.cookie.min.js
959 ms
woocommerce.min.js
954 ms
trp-frontend-compatibility.js
999 ms
NK5LQm4TrwEdS3.js
84 ms
platform.js
30 ms
platform.js
38 ms
wc-blocks.css
135 ms
post-3707.css
132 ms
app.js
133 ms
index.js
134 ms
index.js
163 ms
sourcebuster.min.js
277 ms
order-attribution.min.js
279 ms
jquery.cookie.min.js
276 ms
jquery.magnific-popup.min.js
279 ms
countdown.min.js
279 ms
jquery.slick.min.js
306 ms
typeahead.bundle.min.js
394 ms
handlebars.min.js
384 ms
functions.min.js
382 ms
main.min.js
377 ms
js-large.min.js
384 ms
nasa.functions.min.js
386 ms
nasa.script.min.js
479 ms
webpack-pro.runtime.min.js
503 ms
webpack.runtime.min.js
502 ms
frontend-modules.min.js
503 ms
wp-polyfill-inert.min.js
504 ms
en_GB.png
453 ms
logo-frami.svg
523 ms
untitled.jpg
1714 ms
frami-instalaciones.webp
775 ms
tostador3-430x430.jpg
550 ms
tostador1-430x430.jpg
688 ms
FREIDORA-2-430x430.jpg
698 ms
freidora1-1-430x430.jpg
626 ms
rustidera1-430x430.jpg
690 ms
P30843_l.jpg
728 ms
img-placeholder-430x430.jpg
790 ms
28490b_422dc271018d43a5bd3793e0663fbf7bmv2-430x430.webp
793 ms
FRAMI-VERTICAL.jpg
747 ms
28490b_85274e99e0da47d292c78642d9259d28mv2_d_1464_1702_s_2-430x430.webp
764 ms
28490b_1724e2c1756542a18d9efa091edab4c1mv2-430x430.webp
809 ms
28490b_0ae3a60bf46e4dde9b013b6ee8a40f96mv2-430x430.webp
825 ms
92zPtBhPNqw79Ij1E865zBUv7myjJTVBNI4.woff
25 ms
92zPtBhPNqw79Ij1E865zBUv7myRJTVBNI4.woff
85 ms
92zPtBhPNqw79Ij1E865zBUv7mz9JTVBNI4.woff
119 ms
92zPtBhPNqw79Ij1E865zBUv7mwjJTVBNI4.woff
143 ms
92zPtBhPNqw79Ij1E865zBUv7myjJDVBNI4.woff
145 ms
92zPtBhPNqw79Ij1E865zBUv7mx9IjVBNI4.woff
144 ms
92zPtBhPNqw79Ij1E865zBUv7mxEIjVBNI4.woff
145 ms
92zPtBhPNqw79Ij1E865zBUv7mwjIjVBNI4.woff
147 ms
92zPtBhPNqw79Ij1E865zBUv7mwKIjVBNI4.woff
145 ms
fa-solid-900.woff
917 ms
nasa-font.woff
825 ms
fontawesome-webfont.woff
1013 ms
Pe-icon-7-stroke.woff
880 ms
regenerator-runtime.min.js
784 ms
wp-polyfill.min.js
843 ms
hooks.min.js
893 ms
i18n.min.js
877 ms
frontend.min.js
908 ms
waypoints.min.js
891 ms
core.min.js
891 ms
frontend.min.js
892 ms
elements-handlers.min.js
927 ms
hosteocasion_i.svg
977 ms
1667388378-scaled.jpg
2222 ms
logos.svg
966 ms
frami.es accessibility score
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
frami.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
frami.es SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frami.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 Frami.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.
frami.es
Open Graph description is not detected on the main page of Frami. 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: