3.6 sec in total
386 ms
2.6 sec
621 ms
Welcome to braseirinho.com.br homepage info - get ready to check Braseirinho best content right away, or after learning these important things about braseirinho.com.br
O Braseirinho Restaurante de Frutos do Mar e Sushi, em Curitiba PR, nasceu com o desejo de atender amigos e famílias não só da região, mas de toda Curitiba. Foi realizado um estudo de viabilidade, poi...
Visit braseirinho.com.brWe analyzed Braseirinho.com.br page load time and found that the first response time was 386 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
braseirinho.com.br performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value9.7 s
0/100
25%
Value17.3 s
0/100
10%
Value2,220 ms
6/100
30%
Value0.401
25/100
15%
Value21.3 s
1/100
10%
386 ms
191 ms
193 ms
259 ms
34 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 75% of them (82 requests) were addressed to the original Braseirinho.com.br, 20% (22 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (663 ms) belongs to the original domain Braseirinho.com.br.
Page size can be reduced by 258.7 kB (19%)
1.3 MB
1.1 MB
In fact, the total size of Braseirinho.com.br main page is 1.3 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. 70% of websites need less resources to load. Images take 817.8 kB which makes up the majority of the site volume.
Potential reduce by 253.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 253.6 kB or 84% of the original size.
Potential reduce by 4.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. Braseirinho images are well optimized though.
Potential reduce by 1.0 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.
Number of requests can be reduced by 76 (93%)
82
6
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Braseirinho. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 45 to 1 for CSS and as a result speed up the page load time.
braseirinho.com.br
386 ms
public.css
191 ms
auto-generated-wptwa.css
193 ms
frontend.min.css
259 ms
css
34 ms
frontend.css
216 ms
all.min.css
259 ms
regular.min.css
200 ms
tf-header-footer.css
202 ms
tf-entrace-animation.css
203 ms
cookie-law-info-public.css
268 ms
cookie-law-info-gdpr.css
269 ms
header-footer-elementor.css
271 ms
elementor-icons.min.css
270 ms
frontend.min.css
290 ms
swiper.min.css
327 ms
e-swiper.min.css
334 ms
post-952.css
338 ms
frontend.min.css
336 ms
uael-frontend.min.css
523 ms
vegas.css
360 ms
ytplayer.css
396 ms
tf-simple-slider.css
404 ms
widget-image.min.css
403 ms
widget-text-editor.min.css
401 ms
widget-spacer.min.css
430 ms
shapes.min.css
463 ms
widget-heading.min.css
469 ms
widget-image-gallery.min.css
467 ms
widget-icon-box.min.css
476 ms
widget-social-icons.min.css
502 ms
apple-webkit.min.css
544 ms
widget-star-rating.min.css
544 ms
fluent-forms-public.css
546 ms
fluentform-public-default.css
544 ms
widget-google_maps.min.css
570 ms
post-1408.css
589 ms
css
24 ms
api.js
37 ms
post-564.css
542 ms
astra-addon-66f749f16a3710-92064766.css
487 ms
fontawesome.min.css
490 ms
solid.min.css
419 ms
brands.min.css
458 ms
fluent-forms-elementor-widget.css
465 ms
galleries.min.css
467 ms
cookie-law-info-table.css
469 ms
jquery.min.js
425 ms
jquery-migrate.min.js
461 ms
swiper.min.js
471 ms
cookie-law-info-public.js
465 ms
public.js
542 ms
frontend.min.js
505 ms
anime.min.js
511 ms
textanimation.js
508 ms
tf-animated.js
507 ms
jquery.easing.js
483 ms
vegas.js
453 ms
ytplayer.js
555 ms
typed.js
554 ms
tf-simple-slider.js
553 ms
dom-ready.min.js
527 ms
main.js
493 ms
astra-addon-66f749f16a98e0-99202462.js
492 ms
purify.min.js
561 ms
smush-lazy-load.min.js
555 ms
form-submission.js
528 ms
elfsight-instagram-feed.js
663 ms
webpack-pro.runtime.min.js
484 ms
webpack.runtime.min.js
483 ms
frontend-modules.min.js
561 ms
hooks.min.js
559 ms
i18n.min.js
536 ms
frontend.min.js
515 ms
core.min.js
511 ms
frontend.min.js
562 ms
elements-handlers.min.js
561 ms
fbevents.js
104 ms
slide-1.jpg
580 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
129 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
148 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
147 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
150 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
150 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
149 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf
148 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf
147 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYA.ttf
148 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
151 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf
150 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUZiYA.ttf
150 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf
151 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf
149 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
151 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
151 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
151 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
153 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
153 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
153 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
152 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
153 ms
fa-solid-900.woff
469 ms
fa-regular-400.woff
340 ms
fa-brands-400.woff
524 ms
eicons.woff
430 ms
cropped-logo_braseirinho.pdf-174x58.png
206 ms
leme-navio-2.png
235 ms
paella-braseirinho.png
505 ms
recaptcha__en.js
26 ms
braseirinho.com.br 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
Links do not have a discernible name
braseirinho.com.br 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
braseirinho.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
EN
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Braseirinho.com.br can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Portuguese language. Our system also found out that Braseirinho.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.
braseirinho.com.br
Open Graph data is detected on the main page of Braseirinho. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: