6.4 sec in total
344 ms
5.2 sec
898 ms
Click here to check amazing Juanjez content. Otherwise, check out these important facts you probably never knew about juanjez.com
Custom lettering & typefaces for creative projects | Rotulación y diseño de tipografías a medida para proyectos creativos.
Visit juanjez.comWe analyzed Juanjez.com page load time and found that the first response time was 344 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
juanjez.com performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value10.2 s
0/100
25%
Value15.2 s
1/100
10%
Value700 ms
43/100
30%
Value0.251
49/100
15%
Value19.8 s
2/100
10%
344 ms
773 ms
116 ms
227 ms
311 ms
Our browser made a total of 158 requests to load all elements on the main page. We found that 88% of them (139 requests) were addressed to the original Juanjez.com, 9% (14 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Js.fontdue.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Juanjez.com.
Page size can be reduced by 266.9 kB (15%)
1.8 MB
1.6 MB
In fact, the total size of Juanjez.com main page is 1.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. 80% 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 868.8 kB which makes up the majority of the site volume.
Potential reduce by 235.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 235.6 kB or 89% of the original size.
Potential reduce by 17.5 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. Juanjez images are well optimized though.
Potential reduce by 8.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.
Potential reduce by 5.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. Juanjez.com has all CSS files already compressed.
Number of requests can be reduced by 85 (63%)
135
50
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Juanjez. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 41 to 1 for CSS and as a result speed up the page load time.
juanjez.com
344 ms
www.juanjez.com
773 ms
style.min.css
116 ms
theme.min.css
227 ms
vendors-style.css
311 ms
style.css
430 ms
frontend.css
329 ms
eae.min.css
339 ms
v4-shims.min.css
344 ms
all.min.css
346 ms
vegas.min.css
415 ms
cookie-law-info-public.css
438 ms
cookie-law-info-gdpr.css
463 ms
woocommerce-layout.css
465 ms
woocommerce.css
460 ms
form-themes.css
521 ms
b35b8df.css
657 ms
frontend.css
556 ms
jetwoobuilder-frontend-font.css
573 ms
style.css
575 ms
jet-elements.css
690 ms
jet-elements-skin.css
626 ms
elementor-icons.min.css
672 ms
animations.min.css
684 ms
frontend-legacy.min.css
688 ms
frontend.min.css
836 ms
font-awesome.min.css
766 ms
frontend.min.css
783 ms
post-4373.css
804 ms
frontend.min.css
810 ms
jet-tricks-frontend.css
822 ms
flatpickr.min.css
875 ms
global.css
894 ms
post-4475.css
921 ms
post-4396.css
924 ms
post-4402.css
926 ms
fontawesome.min.css
942 ms
js
63 ms
fontdue.js
164 ms
fontdue.css
285 ms
solid.min.css
979 ms
brands.min.css
891 ms
slider-pro.min.css
813 ms
fontdue-Dwulzzfa.css
144 ms
jquery.js
743 ms
v4-shims.min.js
738 ms
cookie-law-info-public.js
725 ms
webfont.min.js
761 ms
utils.min.js
802 ms
eae.min.js
740 ms
imagesloaded.min.js
732 ms
masonry.min.js
720 ms
animated-main.min.js
729 ms
particles.min.js
761 ms
magnific.min.js
792 ms
vegas.min.js
826 ms
swiper.min.js
818 ms
isotope.pkgd.min.js
774 ms
tilt.jquery.min.js
773 ms
jquery.blockUI.min.js
723 ms
add-to-cart.min.js
686 ms
js.cookie.min.js
791 ms
woocommerce.min.js
779 ms
cart-fragments.min.js
777 ms
underscore.min.js
763 ms
frontend.min.js
703 ms
wp-embed.min.js
689 ms
jquery.smartmenus.min.js
770 ms
url-polyfill.min.js
757 ms
jquery.sliderPro.min.js
760 ms
frontend-modules.min.js
751 ms
jquery.sticky.min.js
713 ms
frontend.min.js
709 ms
position.min.js
765 ms
dialog.min.js
798 ms
waypoints.min.js
797 ms
swiper.min.js
780 ms
share-link.min.js
751 ms
frontend.min.js
716 ms
jet-elements.min.js
767 ms
popperjs.js
749 ms
tippy-bundle.js
739 ms
jet-tricks-frontend.js
738 ms
css
64 ms
frontend.min.js
720 ms
wp-util.min.js
686 ms
frontend.min.js
762 ms
frontend.js
763 ms
flatpickr.min.js
759 ms
juanjez-icon.png
771 ms
schotistext-webfont-1.woff
820 ms
jizBREVNn1dOx-zrZ2X3pZvkTi186zUTiw.ttf
53 ms
jizAREVNn1dOx-zrZ2X3pZvkTi3Q-iI0q14.ttf
90 ms
jizAREVNn1dOx-zrZ2X3pZvkTi20-SI0q14.ttf
125 ms
jizDREVNn1dOx-zrZ2X3pZvkTiUf2zI.ttf
125 ms
jizAREVNn1dOx-zrZ2X3pZvkTi3s-CI0q14.ttf
135 ms
jizAREVNn1dOx-zrZ2X3pZvkTi3A_yI0q14.ttf
136 ms
jizAREVNn1dOx-zrZ2X3pZvkTi2k_iI0q14.ttf
137 ms
jizHREVNn1dOx-zrZ2X3pZvkTiUa41YjjH7J.ttf
137 ms
jizGREVNn1dOx-zrZ2X3pZvkTiUa4_oym1npiA.ttf
135 ms
jizGREVNn1dOx-zrZ2X3pZvkTiUa454xm1npiA.ttf
136 ms
jizBREVNn1dOx-zrZ2X3pZvkTiUa6zUTiw.ttf
137 ms
jizGREVNn1dOx-zrZ2X3pZvkTiUa48Ywm1npiA.ttf
139 ms
jizGREVNn1dOx-zrZ2X3pZvkTiUa4-o3m1npiA.ttf
139 ms
jizGREVNn1dOx-zrZ2X3pZvkTiUa4442m1npiA.ttf
138 ms
schotistext-bold-webfont-1.woff
789 ms
leblancfamily11-light-webfont.woff
696 ms
leblancfamily11-medium-webfont.woff
680 ms
fa-brands-400.woff
810 ms
SchotisDisplay-SemiBold.woff
798 ms
IMG_0466bis-768x508.jpg
896 ms
Captura-de-pantalla-2022-03-28-a-las-20.18.07-768x430.png
969 ms
Seabound_11-768x501.jpg
695 ms
ProyectoRojo-23.svg
713 ms
Proyecto-59.svg
813 ms
Berlanga-58.svg
806 ms
ProyectosRojos-35.svg
806 ms
Proyecto-Verlanga-68.svg
809 ms
ProyectosRojos-37.svg
779 ms
ProyectosRojos-40.svg
799 ms
ProyectosRojos-24.svg
796 ms
ProyectosRojos-36.svg
804 ms
Proyecto-Novedades-69.svg
800 ms
Bazar2021-60.svg
855 ms
ProyectoRojo-21.svg
753 ms
ProyectosRojos-27.svg
758 ms
ProyectosRojos-26.svg
760 ms
ProyectosRojos-22.svg
773 ms
ProyectosRojos-25.svg
767 ms
ProyectosRojos-28.svg
838 ms
ProyectosRojos-34.svg
783 ms
ProyectosRojos-32.svg
785 ms
ProyectosRojos-30.svg
789 ms
P1150808biiis-500x500.jpg
917 ms
Bravas_1080x1080_01-500x500.jpg
807 ms
IMG_2005-500x500.jpg
873 ms
P1130268-e1365330882247-500x445.jpg
788 ms
IMG_2504bs-500x500.jpg
796 ms
www.juanjez.com
1101 ms
IMG_5724bbbis-500x500.jpg
727 ms
Babelia_02-500x500.jpg
775 ms
Calendario_191875-59a6860531094e36bb206371d2f32703-500x500.jpeg
778 ms
IMG_1029bois-500x500.jpg
760 ms
canias3-500x500.jpg
754 ms
P1140941bibis-500x500.jpg
699 ms
Producto-Graveur.svg
776 ms
Producto-Schotis.svg
763 ms
Producto-Xunga.svg
757 ms
Producto-Rotulo.svg
694 ms
Producto-Pliego.svg
691 ms
Producto-Paquito.svg
762 ms
Producto-Show.svg
757 ms
Producto-Ultramarina.svg
760 ms
Producto-BlackPack.svg
693 ms
Producto-HandsUp.svg
724 ms
Producto-Adoquin.svg
802 ms
Producto-Choriza.svg
781 ms
woocommerce-smallscreen.css
112 ms
juanjez.com 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
Links do not have a discernible 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.
juanjez.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
juanjez.com 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 uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Juanjez.com 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 Juanjez.com 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.
juanjez.com
Open Graph data is detected on the main page of Juanjez. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: