1.8 sec in total
38 ms
1.4 sec
379 ms
Click here to check amazing Rafa Barbosa content for Brazil. Otherwise, check out these important facts you probably never knew about rafabarbosa.com
Blog com histórias do dia a dia, resenhas de livros, filmes e séries e conteúdo aleatório da internet.
Visit rafabarbosa.comWe analyzed Rafabarbosa.com page load time and found that the first response time was 38 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
rafabarbosa.com performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value4.0 s
49/100
25%
Value8.1 s
21/100
10%
Value2,180 ms
6/100
30%
Value0.023
100/100
15%
Value14.0 s
10/100
10%
38 ms
410 ms
53 ms
79 ms
67 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 8% of them (6 requests) were addressed to the original Rafabarbosa.com, 26% (19 requests) were made to Encore.scdn.co and 22% (16 requests) were made to Embed-cdn.spotifycdn.com. The less responsive or slowest element that took the longest time to load (468 ms) relates to the external source Open.spotify.com.
Page size can be reduced by 305.6 kB (26%)
1.2 MB
862.0 kB
In fact, the total size of Rafabarbosa.com main page is 1.2 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. 80% 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 552.6 kB which makes up the majority of the site volume.
Potential reduce by 304.7 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 304.7 kB or 82% of the original size.
Potential reduce by 595 B
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. Rafa Barbosa images are well optimized though.
Potential reduce by 278 B
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.
Potential reduce by 45 B
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. Rafabarbosa.com has all CSS files already compressed.
Number of requests can be reduced by 24 (67%)
36
12
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rafa Barbosa. 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 4 to 1 for CSS and as a result speed up the page load time.
rafabarbosa.com
38 ms
rafabarbosa.com
410 ms
gtm.js
53 ms
css
79 ms
218eedcd0d78f271610a75b8366e8054
67 ms
rolo-papel-higienico.jpg
78 ms
37i9dQZF1EMeNYc1EZUDTV
468 ms
gprofiles.js
74 ms
e-202420.js
87 ms
autoptimize_81138f768ccd49a5b4f9b91b8912fdd4.js
41 ms
2020-ano-horrivel.jpg
184 ms
retornando.jpg
103 ms
a-torre-negra-volume-7.jpg
185 ms
save-me-kdrama.jpg
210 ms
rafael.jpg
103 ms
analytics.js
67 ms
hotjar-1145270.js
157 ms
fbevents.js
112 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsWkANDP.woff
100 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhycKkANDP.woff
101 ms
collect
47 ms
pxiByp8kv8JHgFVrLCz7Z1xlEw.woff
42 ms
pxiByp8kv8JHgFVrLEj6Z1xlEw.woff
57 ms
pxiByp8kv8JHgFVrLGT9Z1xlEw.woff
57 ms
pxiEyp8kv8JHgFVrJJfedA.woff
58 ms
fa-solid-900.woff
41 ms
fa-regular-400.woff
60 ms
jizMREVItHgc8qDIbSTKq4XkRiUawTk7f45UM9y05oZ8RODLR-A.woff
198 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff
58 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
57 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff
58 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff
60 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXw.woff
58 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXw.woff
59 ms
collect
54 ms
js
59 ms
modules.1a30a0a67c3c23c13060.js
35 ms
ga-audiences
101 ms
f4338d83daa9ef42.css
22 ms
7ffda23de73b1eea.css
23 ms
3802f0f0fdd596bb.css
27 ms
polyfills-c67a75d1b6f99dc8.js
78 ms
webpack-ce44752480e0e985.js
96 ms
framework-ca706bf673a13738.js
94 ms
main-08df201b32607c28.js
94 ms
_app-f33014b179e9365f.js
105 ms
fec483df-ed779ce1028b7b0c.js
95 ms
7532-9ada25933e41e6fd.js
95 ms
239-6eb6b98f9c269af8.js
118 ms
7469-d0647d58e0606e0e.js
117 ms
4836-25a7c767a2648287.js
115 ms
%5Bid%5D-c346ed281e7fd8b8.js
117 ms
_buildManifest.js
115 ms
_ssgManifest.js
127 ms
CircularSpTitle-Bold-1624fb2df28c20d7203d7fb86ce8b481.woff
71 ms
CircularSpTitle-Black-506746f387a26f25aa3d023b3e501d34.woff
258 ms
CircularSp-Arab-Book-1cd31794cbdd53724469ba03e8573dba.woff
258 ms
CircularSp-Arab-Bold-47ca0fd648a183136981f28d0218cef6.woff
262 ms
CircularSp-Arab-Black-9dda323448d48d7e6cabf84d2df7dc11.woff
260 ms
CircularSp-Hebr-Book-d8209975eafc81a9499df8401a339ddd.woff
257 ms
CircularSp-Hebr-Bold-caa03e4cb8690e726ef1625c7d91a7a5.woff
260 ms
CircularSp-Hebr-Black-f52613a9d541248805af1d0bb33102f8.woff
259 ms
CircularSp-Cyrl-Book-6f078f781ee313e298ad8997fd1ffe3d.woff
258 ms
CircularSp-Cyrl-Bold-7e54bccaf45728c472079785d5cd4519.woff
260 ms
CircularSp-Cyrl-Black-b4305d9bf82554f631d2636c3ef90c54.woff
262 ms
CircularSp-Grek-Book-c9de2c0741586c1ab7b6e95541fc7807.woff
262 ms
CircularSp-Grek-Bold-53bb923248ba22cf5554bbe5f434c5c8.woff
261 ms
CircularSp-Grek-Black-49883536c1a3bfc688235ce40572731d.woff
262 ms
CircularSp-Deva-Book-e1dc3d746b24723f8d3dadb314b97705.woff
264 ms
CircularSp-Deva-Bold-a218ed3bd8e480245847933a79f4ebfb.woff
265 ms
CircularSp-Deva-Black-f1dca2ee660273063af0316d4b7da438.woff
263 ms
CircularSp-Book-3f73da7d35bd81c706bce7bbb84964de.woff
262 ms
CircularSp-Bold-856afe2da4ba4e61239b129e2c16d633.woff
263 ms
rafabarbosa.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
Form elements do not have associated labels
Links do not have a discernible name
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.
rafabarbosa.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
Browser errors were logged to the console
rafabarbosa.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
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 Rafabarbosa.com 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 Rafabarbosa.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.
rafabarbosa.com
Open Graph data is detected on the main page of Rafa Barbosa. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: