877 ms in total
16 ms
693 ms
168 ms
Welcome to rea.global homepage info - get ready to check Rea best content for Indonesia right away, or after learning these important things about rea.global
View International Properties for sale and rent, new developments in popular areas like New York, Los Angeles, San Francisco, London, Italy across the world
Visit rea.globalWe analyzed Rea.global page load time and found that the first response time was 16 ms and then it took 861 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
rea.global performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value7.4 s
4/100
25%
Value8.3 s
19/100
10%
Value4,210 ms
1/100
30%
Value0.256
48/100
15%
Value19.7 s
2/100
10%
16 ms
187 ms
22 ms
38 ms
141 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Rea.global, 77% (46 requests) were made to S3.rea.global and 7% (4 requests) were made to S1.rui.au.reastatic.net. The less responsive or slowest element that took the longest time to load (372 ms) relates to the external source S3.rea.global.
Page size can be reduced by 1.3 MB (55%)
2.4 MB
1.1 MB
In fact, the total size of Rea.global main page is 2.4 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. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 156.0 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 156.0 kB or 85% of the original size.
Potential reduce by 0 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. Rea images are well optimized though.
Potential reduce by 631.6 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 631.6 kB or 44% of the original size.
Potential reduce by 511.6 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. Rea.global needs all CSS files to be minified and compressed as it can save up to 511.6 kB or 85% of the original size.
Number of requests can be reduced by 44 (83%)
53
9
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.rea.global
16 ms
187 ms
utag.js
22 ms
rui-all.min.css
38 ms
a6e8a17d.4616ee07.chunk.css
141 ms
d0e0fa4a4b036c0fbee632f85eabeb51a1dbb969_CSS.4c5e6f59.chunk.css
140 ms
styles.f1302d0d.chunk.css
161 ms
polyfills-5036ab0e351e779f83cf.js
187 ms
95b98745c7115a4e6236ad090c96001665718c45.3bc4b2528f7ac0208cd0.js
204 ms
71.28a365db95f9f1a2a7be.js
206 ms
67.d42719b2d966b228235e.js
204 ms
webpack-94ac1f05304a800a2d46.js
209 ms
framework.a052d0d5f0f2af12ff71.js
208 ms
commons.579d2cb88e6066234aa0.js
203 ms
a73947c3b67aa33b276cbd1f6777b5ca99caaf8d.de0d2282089150f9fd25.js
206 ms
618ccde8e5068d1e6cf299f1b90e1dac3b968a26.9f9e7fad849ac69b5b8e.js
206 ms
main-f3756a859d47c99c88cd.js
251 ms
a6e8a17d.eaf58be72fcea85e662f.js
205 ms
29107295.30154f695499d2e7182a.js
206 ms
ff36a7c755a6dc9701a0fe7e44937d9ff6e5cfbf.279a601dacf7b2cfe622.js
249 ms
1bd03adf4495d0947a63f791a726464c12b8e47c.222b6483f1f9374d3960.js
249 ms
84827581d1f96c4d99c7ad363761915e7d34216e.aca4bfb05c70c5cf020f.js
208 ms
1b31d5ef90dfa1ee4ede0ce3dd938abf28ffe252.2148aaceeb64b26fca91.js
249 ms
2a47e4d5adddeff8dbc09700b04d0e2aac8c29ee.89792974432fd7d4d6bc.js
249 ms
c660fb966c0938edfd1882370c3201eb2ad1ac91.2071d6576da21eb63b1a.js
249 ms
b0cef0a443ac38410b9f2181043580d45f7436e1.7e5cdace147347834850.js
251 ms
f0323608d20e6117923132de4c9c2f521238d7e6.ead78cc8ea4872f75d8a.js
251 ms
8864247e189a32c4a39148757a38b8751029b8e8.7b5e2935fd6966432954.js
251 ms
75b23d780f7cc1d75482e2e7faec18e924d5238e.ea9033cdb88ceafee8e0.js
251 ms
d0e0fa4a4b036c0fbee632f85eabeb51a1dbb969.0ffddbb4379ffec38480.js
340 ms
d0e0fa4a4b036c0fbee632f85eabeb51a1dbb969_CSS.869b0eae3f0cff4d601b.js
340 ms
5260f38b4cc8cbc70ef2b80811e6c0c28cbc7912.933412baf1de7d12b4f9.js
340 ms
90582ade1b2532a9d408ffeb1a700cebd44a1299.2b24e0359be190f9e86c.js
340 ms
dfb6e03f64d4dfed8633c7558e56b88fbc6c5879.0cb9feb7bf2b73e1b197.js
339 ms
_app-ee3f5a4eff080374df50.js
344 ms
f742b0291685852a97feab3bde45087d0d26175f.48aa72301d631a990c45.js
369 ms
0d72668232e65bb3eeb5255bb518ec266349767b.3b297952af8d3316b22c.js
369 ms
f88b3b7f9cf4b7d9c0ce34a1591c38b2c4f3b0c0.11039f9bd6f6943cdd55.js
372 ms
22c0c0204b6f98aaba02355007eb63729a7a879b.c8b33b6bf37f4970cbdc.js
370 ms
abc6f323040e46272c4a0d8579113cb77a8be355.b0615127c00a87cb30b8.js
370 ms
fuse.js
116 ms
59f4a42305e8b5467b9e667bbb12e620f07dd77b.7f5985c116b9b9bd8ea1.js
225 ms
styles.b48cd154ca7e186b492e.js
225 ms
gpn-header-2.jpg
188 ms
logo-footer-sprites.png
66 ms
MuseoSans_300-webfont-34274fbfb2f270b8d53b750c6b779692.otf
161 ms
MuseoSans_500-webfont-8ccea4947561e7008d190f85f414df9c.otf
162 ms
MuseoSans_700-webfont-80acced0ba3630ee652b6d241b1a7f8f.otf
188 ms
HomePage-ff8c5752a438a839752a.js
255 ms
utag.27.js
60 ms
_buildManifest.js
175 ms
_ssgManifest.js
174 ms
us-new-york-ny.jpg
177 ms
us-los-angeles-ca.jpg
237 ms
us-san-francisco-ca.jpg
173 ms
gb-london-england.jpg
174 ms
it.jpg
175 ms
utag.v.js
13 ms
rui-icon.woff
9 ms
museo-sans-500-v1.woff
9 ms
rea.global 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.
rea.global 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
Browser errors were logged to the console
Page has valid source maps
rea.global SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rea.global can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Rea.global 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.
rea.global
Open Graph description is not detected on the main page of Rea. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: