6.9 sec in total
391 ms
5.9 sec
602 ms
Welcome to clg.com.do homepage info - get ready to check Clg best content right away, or after learning these important things about clg.com.do
Visit clg.com.doWe analyzed Clg.com.do page load time and found that the first response time was 391 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
clg.com.do performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value12.1 s
0/100
25%
Value6.8 s
34/100
10%
Value1,780 ms
10/100
30%
Value0.327
35/100
15%
Value13.7 s
11/100
10%
391 ms
131 ms
817 ms
1206 ms
130 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Clg.com.do, 7% (11 requests) were made to Maps.googleapis.com and 7% (10 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Clgmediagroup.com.
Page size can be reduced by 1.8 MB (46%)
3.8 MB
2.0 MB
In fact, the total size of Clg.com.do main page is 3.8 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. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 51.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 51.8 kB or 81% of the original size.
Potential reduce by 163.5 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. Clg images are well optimized though.
Potential reduce by 989.0 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 989.0 kB or 71% of the original size.
Potential reduce by 561.4 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. Clg.com.do needs all CSS files to be minified and compressed as it can save up to 561.4 kB or 86% of the original size.
Number of requests can be reduced by 78 (55%)
143
65
The browser has sent 143 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Clg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
www.clgmediagroup.com
391 ms
agencia
131 ms
817 ms
1206 ms
wp-emoji-release.min.js
130 ms
dp_fontello.css
134 ms
styles.css
134 ms
settings.css
172 ms
dpcss_min.css
141 ms
override.css
142 ms
override-plugins.css
197 ms
js_composer_front.css
199 ms
dp_vc_frontend.css
204 ms
dynamic-css.php
918 ms
style4.css
225 ms
jquery.js
355 ms
jquery-migrate.min.js
260 ms
jquery.themepunch.tools.min.js
328 ms
jquery.themepunch.revolution.min.js
326 ms
jquery.mCustomScrollbar.concat.min.js
287 ms
selectFix.js
323 ms
modernizr.custom.js
353 ms
flexslider.css
388 ms
comment-reply.min.js
389 ms
jquery.form.min.js
396 ms
scripts.js
417 ms
tabs.js
416 ms
jquery.noconflict.js
452 ms
easing.js
450 ms
jquery.fitvid.js
459 ms
froogaloop.min.js
479 ms
jquery.prettyPhoto.js
480 ms
jquery.mb.YTPlayer.min.js
516 ms
appear.js
514 ms
jquery-easypiechart-min.js
523 ms
jquery.zflickrfeed.min.js
541 ms
jquery.tipsy.js
542 ms
jquery.jplayer.min.js
579 ms
waypoints.min.js
579 ms
owl.carousel.min.js
604 ms
jquery.parallax.js
505 ms
fontello.css
505 ms
ss-gizmo.css
541 ms
picons.css
528 ms
gallery.css
556 ms
normalize.css
531 ms
template.css
499 ms
wp.css
524 ms
stuff.css
523 ms
wp.extensions.css
530 ms
extensions.css
502 ms
shortcodes.css
468 ms
animate.css
465 ms
prettyPhoto.css
467 ms
jquery.mCustomScrollbar.css
494 ms
owl.css
470 ms
slider.flexslider.css
472 ms
shortcodes.js
466 ms
dp.scripts.js
467 ms
like.js
487 ms
dp.menu.js
469 ms
jquery.isotope.min.js
476 ms
frontend.js
573 ms
wp-embed.min.js
572 ms
js_composer_front.js
573 ms
jquery.flexslider-min.js
554 ms
waypoints.min.js
552 ms
logo21.png
112 ms
facebook-CLG-template.jpg
281 ms
shutterstock_108686414-u224-fr.jpg
737 ms
slider-bg2.jpg
277 ms
b42-570x326.jpg
157 ms
01.jpg
276 ms
02.jpg
281 ms
web7500-298x298.jpg
277 ms
web3500-298x298.jpg
277 ms
web2500-298x298.jpg
279 ms
web500-298x298.jpg
279 ms
web4500-298x298.jpg
726 ms
web5500-298x298.jpg
727 ms
web6500-298x298.jpg
727 ms
logo1500-298x298.jpg
731 ms
logo2500-298x298.jpg
732 ms
logo3500-298x298.jpg
733 ms
logo5500-298x298.jpg
734 ms
logo7500-298x298.jpg
735 ms
logo8500-298x298.jpg
735 ms
logo10500-298x298.jpg
736 ms
logo13500-298x298.jpg
736 ms
logo11500-298x298.jpg
737 ms
logo12500-298x298.jpg
738 ms
logo14500-298x298.jpg
738 ms
altamar.jpg
739 ms
dux.jpg
740 ms
lanacional.jpg
740 ms
paradisuspc.jpg
742 ms
puntacana.png
740 ms
unibe.jpg
698 ms
scotiabank.jpg
696 ms
palmareal.png
689 ms
hardrockhotel.jpg
688 ms
eps.jpg
688 ms
fontello.woff
984 ms
piconsthin.woff
647 ms
embed
614 ms
ss-gizmo.woff
481 ms
back-top.png
479 ms
parallax2.jpg
366 ms
loader.gif
295 ms
ajax-loader.gif
295 ms
js
326 ms
init_embed.js
291 ms
revicons.woff
236 ms
slider-bg2-thm.jpg
626 ms
slider-bg1-thm1.jpg
601 ms
desktop.small.css
73 ms
common.js
51 ms
map.js
78 ms
google4.png
113 ms
overlay.js
112 ms
util.js
110 ms
onion.js
110 ms
search_impl.js
111 ms
tablet.css
110 ms
stats.js
56 ms
openhand_8_8.cur
63 ms
ViewportInfoService.GetViewportInfo
158 ms
ViewportInfoService.GetViewportInfo
49 ms
kh
76 ms
transparent.png
60 ms
tablet.small.css
98 ms
controls.js
19 ms
css
134 ms
entity11.png
68 ms
mapcnt6.png
77 ms
sv5.png
77 ms
mobile.css
94 ms
tmapctrl.png
48 ms
vt
59 ms
vt
116 ms
vt
90 ms
vt
85 ms
vt
88 ms
vt
86 ms
vt
95 ms
vt
163 ms
vt
122 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
27 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
38 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
46 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
46 ms
clg.com.do accessibility score
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
clg.com.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
clg.com.do SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Clg.com.do can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Clg.com.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.
clg.com.do
Open Graph description is not detected on the main page of Clg. 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: