4.5 sec in total
533 ms
1.8 sec
2.2 sec
Click here to check amazing RODRIGOHENRIK content. Otherwise, check out these important facts you probably never knew about rodrigohenrik.com
Eu ajudo você a aumentar suas vendas online através da Otimização da Taxa de Conversão (CRO/UX).
Visit rodrigohenrik.comWe analyzed Rodrigohenrik.com page load time and found that the first response time was 533 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
rodrigohenrik.com performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value2.2 s
95/100
25%
Value2.2 s
99/100
10%
Value0 ms
100/100
30%
Value0.001
100/100
15%
Value2.2 s
99/100
10%
533 ms
11 ms
18 ms
8 ms
15 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Rodrigohenrik.com, 21% (13 requests) were made to Assets.tumblr.com and 15% (9 requests) were made to 40.media.tumblr.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source 40.media.tumblr.com.
Page size can be reduced by 1.3 MB (33%)
3.9 MB
2.6 MB
In fact, the total size of Rodrigohenrik.com main page is 3.9 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. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 113.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. This page needs HTML code to be minified as it can gain 36.9 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 113.9 kB or 83% of the original size.
Potential reduce by 220.6 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. RODRIGOHENRIK images are well optimized though.
Potential reduce by 695.5 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 695.5 kB or 65% of the original size.
Potential reduce by 245.2 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. Rodrigohenrik.com needs all CSS files to be minified and compressed as it can save up to 245.2 kB or 82% of the original size.
Number of requests can be reduced by 16 (30%)
54
38
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of RODRIGOHENRIK. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
rodrigohenrik.com
533 ms
pre_tumblelog.js
11 ms
main-min.css
18 ms
tumblelog_post_message_queue.js
8 ms
stylesheet.css
15 ms
jquery.min.js
10 ms
main-min.js
78 ms
index.js
88 ms
avatar_3b666d08f515_128.png
241 ms
tumblr_inline_nzrmkx4gS31tehz2w_1280.png
481 ms
y7WD8dlU6UU
415 ms
tumblr_inline_nzrmof3F841tehz2w_1280.png
247 ms
like_iframe.html
245 ms
tumblr_inline_nzrn1dbhjc1tehz2w_1280.png
590 ms
tumblr_inline_nwappmGtUA1tehz2w_1280.png
1152 ms
tumblr_inline_nwa4utQOKZ1tehz2w_1280.png
747 ms
tumblr_inline_nw9xwcsiIx1tehz2w_1280.jpg
765 ms
tumblr_inline_nw9xx10wd01tehz2w_1280.jpg
979 ms
tumblr_inline_nw9xznsFSQ1tehz2w_1280.jpg
593 ms
tumblr_inline_nw9y046Pha1tehz2w_1280.jpg
591 ms
tumblr_nw7zjuZmNU1uj5xnmo1_1280.jpg
709 ms
tumblr_inline_nw89cxR1sw1tehz2w_540.gif
251 ms
tumblr_static_tumblr_static_a9f08vtdttkw8s8kg4k4400gk_focused_v3.jpg
379 ms
tumblr_inline_nzrlxgwf4h1tehz2w_1280.png
249 ms
tumblr_nwa23y9bX71uj5xnm_og_1280.jpg
245 ms
tumblr_inline_nw9xzlaMtI1tehz2w_1280.jpg
372 ms
tumblr_inline_nw9xzqMrTa1tehz2w_1280.jpg
374 ms
tumblr_inline_nw9y01IxJO1tehz2w_1280.jpg
221 ms
tumblr_inline_nw9y09XAWs1tehz2w_1280.jpg
218 ms
tumblr_inline_nw9y071WHP1tehz2w_1280.jpg
247 ms
tumblr_nw7zftvRlu1uj5xnmo1_1280.png
248 ms
impixu
367 ms
impixu
371 ms
analytics.html
575 ms
Lorimer_No2_Semibold-webfont.woff
11 ms
Lorimer_No2_Cnd_Medium-webfont.woff
33 ms
Gibson-Regular-webfont.woff
34 ms
Gibson-SemiBold-webfont.woff
32 ms
8EN1DX6pvX3m1fBD9AETcHqcA
6 ms
login_check.html
31 ms
avatar_3b666d08f515_40.png
39 ms
iframe_logo.png
225 ms
www-embed-player-vflfNyN_r.css
24 ms
www-embed-player.js
46 ms
base.js
92 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
68 ms
ad_status.js
66 ms
rapid-3.36.js
149 ms
rapidworker-1.2.js
148 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
122 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
140 ms
ga.js
78 ms
analytics.js
58 ms
cs.js
75 ms
addthis.html
112 ms
yql
262 ms
__utm.gif
19 ms
addthis_widget.js
47 ms
api.html
49 ms
300lo.json
52 ms
sh.8e5f85691f9aaa082472a194.html
48 ms
cedexis.radar.js
5 ms
rodrigohenrik.com 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
rodrigohenrik.com 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
rodrigohenrik.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
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rodrigohenrik.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Rodrigohenrik.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.
rodrigohenrik.com
Open Graph data is detected on the main page of RODRIGOHENRIK. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: