3.2 sec in total
404 ms
2.3 sec
515 ms
Click here to check amazing Pr Paulo content for Brazil. Otherwise, check out these important facts you probably never knew about prpaulo.com
Twitter: @prpaulocesar Instagram: pcsantos10
Visit prpaulo.comWe analyzed Prpaulo.com page load time and found that the first response time was 404 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
prpaulo.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value6.5 s
9/100
25%
Value6.6 s
38/100
10%
Value5,240 ms
0/100
30%
Value0.02
100/100
15%
Value11.8 s
17/100
10%
404 ms
14 ms
26 ms
23 ms
24 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Prpaulo.com, 14% (16 requests) were made to Static.tumblr.com and 12% (14 requests) were made to 33.media.tumblr.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Badge.facebook.com.
Page size can be reduced by 566.9 kB (28%)
2.0 MB
1.5 MB
In fact, the total size of Prpaulo.com main page is 2.0 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 49.8 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 49.8 kB or 77% of the original size.
Potential reduce by 38.3 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. Pr Paulo images are well optimized though.
Potential reduce by 368.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 368.5 kB or 63% of the original size.
Potential reduce by 110.3 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. Prpaulo.com needs all CSS files to be minified and compressed as it can save up to 110.3 kB or 71% of the original size.
Number of requests can be reduced by 41 (38%)
109
68
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pr Paulo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.prpaulo.com
404 ms
pre_tumblelog.js
14 ms
pictos.css
26 ms
titillium.css
23 ms
style.css
24 ms
jquery.min.js
33 ms
tumblelog_post_message_queue.js
19 ms
stylesheet.css
26 ms
plugins.min.js
27 ms
script.min.js
25 ms
placard-v2.min.js
25 ms
placard.min.css
25 ms
index.js
24 ms
bottom-bg.gif
155 ms
avatar_0fd8a557eb12_30.png
154 ms
1307575279.1636.1459906532.png
1686 ms
tumblr_inline_o48nyg5mKu1qcbsyy_500.jpg
297 ms
uKP4qo2fy
368 ms
tumblr_o3weqy5rTb1qd5te8o1_500.jpg
147 ms
follow_button.html
182 ms
plusone.js
299 ms
widgets.js
146 ms
ga.js
175 ms
impixu
396 ms
widgets.js
80 ms
avatar_ef0bd1909e11_24.png
254 ms
avatar_9ba350e2777e_24.png
192 ms
381 ms
avatar_f6a3bf932961_24.png
321 ms
avatar_db722a134cda_24.png
327 ms
avatar_2a12593bcddd_24.png
342 ms
avatar_92cda48a1bb7_24.png
329 ms
tumblr_inline_o46gvtpU911qcbsyy_500.jpg
288 ms
tumblr_novsqqesnk1r93mdvo1_250.jpg
184 ms
tumblr_novssjziOv1r93mdvo1_250.jpg
183 ms
tumblr_np4bi5TYO51r93mdvo1_250.jpg
233 ms
tumblr_nb1dq7HxQi1rbb7p1o1_250.jpg
241 ms
tumblr_ncom3zMuV21r5n32vo1_250.jpg
241 ms
tumblr_n8u0saIL361qhgj6yo1_250.jpg
240 ms
tumblr_mqt3zgZgaK1qjdiw3o1_250.jpg
240 ms
avatar_e1c58a401774_24.png
179 ms
avatar_113d863f29e0_24.png
178 ms
impixu
286 ms
avatar_682c09618c52_24.png
67 ms
avatar_4d7ca3671d98_24.png
70 ms
avatar_26d8b5c0acfa_24.png
179 ms
avatar_62c86649c6c6_24.png
70 ms
avatar_3d6f06531f8e_24.png
70 ms
avatar_1533d8a0c9a3_24.png
69 ms
avatar_9a6d012e2af6_24.png
173 ms
avatar_8428d08080f5_24.png
172 ms
avatar_fbe7eddc13e9_24.png
172 ms
avatar_ddbc6c1dcf8b_24.png
152 ms
avatar_ddb3187dcc97_24.png
172 ms
avatar_6d15fde8da28_24.png
180 ms
tumblr_static_novo_banner_tumblr.jpg
295 ms
article-footer-bg.gif
65 ms
social-icons.png
65 ms
_sprites-dark.png
64 ms
loading.gif
63 ms
controls.png
63 ms
tumblr_n30uo7SdmW1r93mdvo1_250.jpg
63 ms
analytics.html
248 ms
4A0JgFjIAAA==
20 ms
titilliumtext22l001-webfont.woff
141 ms
titilliumtext22l003-webfont.woff
142 ms
login_check.html
54 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
243 ms
follow_button.js
116 ms
__utm.gif
145 ms
avatar_0fd8a557eb12_40.png
168 ms
iframe_logo.png
134 ms
analytics.js
71 ms
cb=gapi.loaded_0
27 ms
__utm.gif
59 ms
signup_to_answer.css
56 ms
rapid-3.36.js
80 ms
rapidworker-1.2.js
82 ms
syndication
137 ms
321217244266897410
285 ms
ga.js
92 ms
analytics.js
64 ms
cs.js
80 ms
1389084_474416162741472_671899986_n.jpg
514 ms
12751525_1733189783566811_1849020401_n.jpg
744 ms
12797896_1699652383611416_215891489_n.jpg
881 ms
12383137_197898033910051_1917635380_n.jpg
806 ms
__utm.gif
10 ms
proxy.jpg
130 ms
proxy.jpg
122 ms
proxy.jpg
118 ms
proxy.jpg
116 ms
proxy.jpg
121 ms
proxy.jpg
164 ms
proxy.jpg
169 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
44 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
54 ms
R0h5OpEW_normal.jpeg
137 ms
mIHy3wZd_normal.jpeg
67 ms
LXf1BcCm_normal.jpg
68 ms
Cdm_g1wWwAQ-qhE.jpg:small
99 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
67 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
92 ms
proxy.jpg
45 ms
proxy.jpg
31 ms
proxy.jpg
49 ms
proxy.jpg
31 ms
proxy.jpg
29 ms
proxy.jpg
52 ms
proxy.jpg
55 ms
jot.html
2 ms
jot
24 ms
cedexis.radar.js
4 ms
prpaulo.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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
prpaulo.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
prpaulo.com 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
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prpaulo.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Prpaulo.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.
prpaulo.com
Open Graph data is detected on the main page of Pr Paulo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: