2.9 sec in total
882 ms
1.6 sec
396 ms
Click here to check amazing Franquia content for Brazil. Otherwise, check out these important facts you probably never knew about franquia.com.br
Aprenda como abrir uma franquia do zero com este guia atualizado. Processo completo, documentos, custos, COF e erros para evitar. Comece certo!
Visit franquia.com.brWe analyzed Franquia.com.br page load time and found that the first response time was 882 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
franquia.com.br performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value4.3 s
42/100
25%
Value4.4 s
74/100
10%
Value430 ms
65/100
30%
Value0.214
58/100
15%
Value5.4 s
71/100
10%
882 ms
54 ms
61 ms
58 ms
58 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 89% of them (48 requests) were addressed to the original Franquia.com.br, 9% (5 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (882 ms) belongs to the original domain Franquia.com.br.
Page size can be reduced by 270.2 kB (19%)
1.5 MB
1.2 MB
In fact, the total size of Franquia.com.br main page is 1.5 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. 45% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 117.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 117.9 kB or 83% of the original size.
Potential reduce by 88.0 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. Franquia images are well optimized though.
Potential reduce by 35.9 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 35.9 kB or 21% of the original size.
Potential reduce by 28.5 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. Franquia.com.br needs all CSS files to be minified and compressed as it can save up to 28.5 kB or 39% of the original size.
Number of requests can be reduced by 36 (75%)
48
12
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Franquia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
franquia.com.br
882 ms
frontend.css
54 ms
style.min.css
61 ms
theme.min.css
58 ms
header-footer.min.css
58 ms
frontend-lite.min.css
84 ms
post-10.css
61 ms
swiper.min.css
82 ms
frontend-lite.min.css
76 ms
post-12.css
88 ms
post-18.css
80 ms
post-167.css
94 ms
css
30 ms
widget-nav-menu.min.css
102 ms
widget-icon-box.min.css
95 ms
widget-loop-builder.min.css
100 ms
hello-frontend.min.js
84 ms
wpmssab.min.js
108 ms
SmoothScroll.min.js
109 ms
wpmss.min.js
110 ms
smush-lazy-load.min.js
111 ms
jquery.min.js
151 ms
jquery-migrate.min.js
149 ms
jquery.smartmenus.min.js
147 ms
imagesloaded.min.js
149 ms
webpack-pro.runtime.min.js
162 ms
webpack.runtime.min.js
164 ms
frontend-modules.min.js
164 ms
wp-polyfill-inert.min.js
161 ms
regenerator-runtime.min.js
162 ms
wp-polyfill.min.js
166 ms
hooks.min.js
165 ms
i18n.min.js
167 ms
frontend.min.js
169 ms
waypoints.min.js
168 ms
core.min.js
172 ms
frontend.min.js
196 ms
elements-handlers.min.js
156 ms
jquery.sticky.min.js
150 ms
Rectangle-2.png
197 ms
galeria_tricot___loja_online_logo.jpeg
102 ms
franquia-oticas-carol-franchise-store.jpg
90 ms
Logo-prudential-do-brasil.png
127 ms
logo-pizza-cesar.jpeg
97 ms
franquia-crepefy-franchise-store-1.png
127 ms
franquia-mestre-cervejeiro-franchise-store.jpg
127 ms
Group.png
118 ms
Horizontal-icon.svg
85 ms
Group-15.png
150 ms
Qw3AZQpJHj_6LzHUngWbrFkDH1x9Uzk0jbs5.woff
100 ms
Qw3AZQpJHj_6LzHUngWbrFkDH1x9ajk0jbs5.woff
168 ms
Qw3AZQpJHj_6LzHUngWbrFkDH1x9hj40jbs5.woff
201 ms
Qw3AZQpJHj_6LzHUngWbrFkDH1x9tD40jbs5.woff
152 ms
Qw3AZQpJHj_6LzHUngWbrFkDH1x96j40jbs5.woff
185 ms
franquia.com.br accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA IDs are not unique
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
Links do not have a discernible name
franquia.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
franquia.com.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
![]()
PT
![]()
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Franquia.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Franquia.com.br 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.
franquia.com.br
Open Graph data is detected on the main page of Franquia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: