1.8 sec in total
176 ms
1.5 sec
119 ms
Visit frankizia.com now to see the best up-to-date Frankizia content and also check out these interesting facts you probably never knew about frankizia.com
Consultores en franquicias. Servicios de consultoría para franquiciadores. Expansión nacional e internacional, gestión de redes, formación, jurídico.
Visit frankizia.comWe analyzed Frankizia.com page load time and found that the first response time was 176 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
frankizia.com performance score
name
value
score
weighting
Value13.8 s
0/100
10%
Value29.9 s
0/100
25%
Value26.9 s
0/100
10%
Value2,520 ms
4/100
30%
Value0.035
100/100
15%
Value35.1 s
0/100
10%
176 ms
87 ms
64 ms
71 ms
70 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Frankizia.com, 49% (35 requests) were made to Static.parastorage.com and 17% (12 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (457 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.6 MB (71%)
3.7 MB
1.1 MB
In fact, the total size of Frankizia.com main page is 3.7 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. Javascripts take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 95.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 95.9 kB or 84% of the original size.
Potential reduce by 30.8 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. Frankizia images are well optimized though.
Potential reduce by 2.3 MB
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 2.3 MB or 76% of the original size.
Potential reduce by 148.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. Frankizia.com needs all CSS files to be minified and compressed as it can save up to 148.0 kB or 87% of the original size.
Number of requests can be reduced by 46 (74%)
62
16
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frankizia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.frankizia.com
176 ms
bt
87 ms
require.min.js
64 ms
main-r.min.js
71 ms
viewer.css
70 ms
dynamicmodel
53 ms
4f9566_8c4007660cecae397350e99b55c1413a_303.json.z
410 ms
4f9566_33ce959d91a57f1c9472c20835d85a30_302.json.z
408 ms
ugc-viewer
48 ms
bt
163 ms
skins.min.js
168 ms
components.min.js
156 ms
utils.min.js
59 ms
core.min.js
161 ms
react-with-addons.min.js
55 ms
lodash.min.js
41 ms
TweenMax.min.js
146 ms
layout.min.js
144 ms
tpa.min.js
143 ms
fonts.min.js
146 ms
animations.min.js
143 ms
swfobject.min.js
144 ms
mousetrap.min.js
147 ms
tweenEngine.min.js
146 ms
DrawSVGPlugin.min.js
145 ms
react-dom.min.js
147 ms
ScrollToPlugin.min.js
148 ms
widgets.min.js
148 ms
experiment.js
155 ms
render.min.js
147 ms
wixappsCore.min.js
148 ms
wixappsClassics.min.js
151 ms
wixappsBuilder.min.js
146 ms
zepto.min.js
150 ms
color.min.js
150 ms
react-dom-server.min.js
150 ms
bt
50 ms
latin.css
22 ms
dc.js
229 ms
bt
227 ms
8d2c2a4846503b9067e2fd2f590445c2.wix_mp
143 ms
arrows_white_new3.png
91 ms
css
90 ms
fe7017590fbd384c7502a64601c7b444.png
50 ms
0e3ab593d41f9b50a377e56363e64221.png
50 ms
26bc2839a705968b533a2c44afdb43c3.wix_mp
64 ms
4f9566_20406efb1908467d801cedaed440eaa3.jpg
453 ms
4f9566_d0f884a1627a4833ab1b408a3af84c4a.jpg
457 ms
4f9566_28e9a942b28d459fa1d2e5bdbde0cada.jpg
310 ms
4f9566_12d854ec8cac42539dd2169a1e2e3e28.jpg
450 ms
4f9566_afd6e84cb3ea44a2ab88e0043f53c333.jpg
259 ms
4f9566_e4cbab2b2907d864507045a948bd9736.png
219 ms
bt
61 ms
bt
61 ms
bt
174 ms
shiny1button_bg.png
62 ms
155086705
242 ms
__utm.gif
19 ms
opensans-regular-webfont.woff
117 ms
opensans-bold-webfont.woff
14 ms
BaRU3GSISDJW2nIqbysbmg.ttf
11 ms
PeTTkHQKj5rUPVxkIGAoaw.ttf
116 ms
j7wx-rRiDuE-JcaZ1ilpKg.ttf
116 ms
c5749443-93da-4592-b794-42f28d62ef72.woff
22 ms
player.js
125 ms
player.css
97 ms
ga.js
24 ms
vuid.min.js
122 ms
__utm.gif
31 ms
ugc-viewer
67 ms
proxy.html
43 ms
frankizia.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
<frame> or <iframe> elements do not have a title
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
frankizia.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
Missing source maps for large first-party JavaScript
frankizia.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
Tap targets are not sized appropriately
ES
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frankizia.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Frankizia.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.
frankizia.com
Open Graph data is detected on the main page of Frankizia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: