3.3 sec in total
720 ms
2.2 sec
428 ms
Click here to check amazing M2 content for Dominican Republic. Otherwise, check out these important facts you probably never knew about m2.do
Casas y apartamentos en venta y alquiler - Santo Domingo, Santiago, Punta Cana - Villas y solares en República Dominicana
Visit m2.doWe analyzed M2.do page load time and found that the first response time was 720 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
m2.do performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value20.7 s
0/100
25%
Value12.7 s
3/100
10%
Value1,500 ms
14/100
30%
Value0.003
100/100
15%
Value17.9 s
4/100
10%
720 ms
453 ms
277 ms
24 ms
185 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 33% of them (14 requests) were addressed to the original M2.do, 12% (5 requests) were made to Pagead2.googlesyndication.com and 12% (5 requests) were made to Themes.googleusercontent.com. The less responsive or slowest element that took the longest time to load (720 ms) belongs to the original domain M2.do.
Page size can be reduced by 223.3 kB (30%)
743.9 kB
520.5 kB
In fact, the total size of M2.do main page is 743.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 365.4 kB which makes up the majority of the site volume.
Potential reduce by 26.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 26.7 kB or 77% of the original size.
Potential reduce by 8.1 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. M2 images are well optimized though.
Potential reduce by 65.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 65.5 kB or 33% of the original size.
Potential reduce by 123.0 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. M2.do needs all CSS files to be minified and compressed as it can save up to 123.0 kB or 84% of the original size.
Number of requests can be reduced by 10 (31%)
32
22
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
m2.do
720 ms
bootstrap.min.css
453 ms
style.css
277 ms
css
24 ms
ajax_v2.js
185 ms
adsbygoogle.js
9 ms
jquery.min.js
77 ms
bootstrap.min.js
197 ms
Casa-564-M2-En-Arroyo-Hondo-Iii-Santo-Domingo-14061487891545958627-400x300.jpg
470 ms
Apartamento-En-Venta--Evaristo-Morales--Santo-Domingo-14050040402105665330-400x300.jpg
473 ms
Casa-En-Venta--Don-Honorio--Santo-Domingo-1405002839866465725-400x300.jpg
475 ms
m2_logo.png
102 ms
product_marketing_module_1_v2.png
213 ms
agente_pro.jpg
213 ms
rent_buy.jpg
102 ms
analytics.js
14 ms
bg-search-box-apt.jpg
467 ms
bg-search-box-apt-inner.png
198 ms
collect
34 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
28 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
30 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
29 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
30 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
30 ms
glyphicons-halflings-regular.woff
235 ms
arrow.jpg
141 ms
ca-pub-0243119537643981.js
82 ms
zrt_lookup.html
144 ms
show_ads_impl.js
69 ms
main_imgsheet_20120106.png
240 ms
ads
345 ms
osd.js
8 ms
Casa-564-M2-En-Arroyo-Hondo-Iii-Santo-Domingo-14061487891545958627-400x300.jpg
580 ms
Apartamento-En-Venta--Evaristo-Morales--Santo-Domingo-14050040402105665330-400x300.jpg
572 ms
Casa-En-Venta--Don-Honorio--Santo-Domingo-1405002839866465725-400x300.jpg
482 ms
4159908458326975756
36 ms
abg.js
39 ms
m_js_controller.js
52 ms
googlelogo_color_112x36dp.png
36 ms
s
33 ms
x_button_blue2.png
33 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
5 ms
m2.do accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
m2.do 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
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
m2.do 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
ES
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M2.do can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that M2.do 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.
m2.do
Open Graph description is not detected on the main page of M2. 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: