Tools & Wizards About Us
dominos.com.do screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

dominos.com.do

Domino's Home Page - Domino's Pizza, Order Pizza Online for Delivery - Dominos.com

Page Load Speed

1.8 sec in total

First Response

192 ms

Resources Loaded

1.5 sec

Page Rendered

64 ms

dominos.com.do screenshot

About Website

Welcome to dominos.com.do homepage info - get ready to check Domino S best content for Dominican Republic right away, or after learning these important things about dominos.com.do

Pide Domino's en linea para domicilio o recoger en tienda. Tenemos deliciosas pizzas, acompañamientos, bebidas y postres. Pide ahora!

Visit dominos.com.do

Key Findings

We analyzed Dominos.com.do page load time and found that the first response time was 192 ms and then it took 1.6 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.

Performance Metrics

dominos.com.do performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value17.5 s

0/100

25%

SI (Speed Index)

Value9.3 s

12/100

10%

TBT (Total Blocking Time)

Value2,290 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.138

79/100

15%

TTI (Time to Interactive)

Value24.6 s

0/100

10%

Network Requests Diagram

www.dominos.com.do

192 ms

screen.css

62 ms

screen.desktop.css

52 ms

screen.fixed.css

58 ms

homepage.css

93 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Dominos.com.do, 94% (102 requests) were made to Cache.dominos.com and 1% (1 request) were made to Cdn.raygun.io. The less responsive or slowest element that took the longest time to load (383 ms) relates to the external source Cache.dominos.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.1 MB (61%)

Content Size

5.0 MB

After Optimization

1.9 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Dominos.com.do main page is 5.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. Only a small number of websites need less resources to load. Javascripts take 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 42.7 kB

  • Original 58.5 kB
  • After minification 56.5 kB
  • After compression 15.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 42.7 kB or 73% of the original size.

JavaScript Optimization

-63%

Potential reduce by 3.0 MB

  • Original 4.7 MB
  • After minification 4.7 MB
  • After compression 1.8 MB

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 3.0 MB or 63% of the original size.

CSS Optimization

-25%

Potential reduce by 55.3 kB

  • Original 217.3 kB
  • After minification 217.3 kB
  • After compression 161.9 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. Dominos.com.do needs all CSS files to be minified and compressed as it can save up to 55.3 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 103 (96%)

Requests Now

107

After Optimization

4

  • AJAX
  • JavaScript
  • CSS

The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Domino S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 98 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.dominos.com.do

www.dominos.com.do

192 ms

screen.css

screen.css

62 ms

screen.desktop.css

screen.desktop.css

52 ms

screen.fixed.css

screen.fixed.css

58 ms

homepage.css

homepage.css

93 ms

homepage.desktop.css

homepage.desktop.css

108 ms

homepage.fixed.css

homepage.fixed.css

110 ms

override.min.css

override.min.css

113 ms

xdomain.js

xdomain.js

194 ms

core-js-bundle.js

core-js-bundle.js

135 ms

bootlibs.js

bootlibs.js

110 ms

dpz.roloRedirect.js

dpz.roloRedirect.js

109 ms

boot.js

boot.js

109 ms

base-site.js

base-site.js

137 ms

home-site.js

home-site.js

133 ms

scripts.js

scripts.js

132 ms

raygun.min.js

raygun.min.js

24 ms

4KTV2-QRXXN-6JH3L-VGPDD-BJ5DR

4KTV2-QRXXN-6JH3L-VGPDD-BJ5DR

50 ms

config.json

config.json

173 ms

dayjs.min.js

dayjs.min.js

92 ms

customParseFormat.js

customParseFormat.js

91 ms

advancedFormat.js

advancedFormat.js

90 ms

updateLocale.js

updateLocale.js

92 ms

dpz.marketConfig.js

dpz.marketConfig.js

217 ms

dpz.masterKillConfig.js

dpz.masterKillConfig.js

114 ms

ua-parser.min.js

ua-parser.min.js

114 ms

dpz.createCanonical.js

dpz.createCanonical.js

114 ms

dpz.couponServiceMethodWarning.js

dpz.couponServiceMethodWarning.js

113 ms

dpz.oauth.constants.js

dpz.oauth.constants.js

114 ms

dpz.lang.errors.js

dpz.lang.errors.js

187 ms

dpz.lang.confirmation.js

dpz.lang.confirmation.js

110 ms

dpz.seo.js

dpz.seo.js

107 ms

dpz.lang.titles.js

dpz.lang.titles.js

130 ms

dpz.storeVariance.js

dpz.storeVariance.js

107 ms

dpz.orderCapacity.js

dpz.orderCapacity.js

160 ms

dpz.hotspots.js

dpz.hotspots.js

107 ms

dpz.serviceMethod.constants.js

dpz.serviceMethod.constants.js

121 ms

dpz.thresholdCoupons.js

dpz.thresholdCoupons.js

107 ms

constants.js

constants.js

108 ms

dpz.lang.errorsValidator.js

dpz.lang.errorsValidator.js

122 ms

dpz.lang.locations.js

dpz.lang.locations.js

192 ms

dpz.lang.general.js

dpz.lang.general.js

168 ms

dpz.lang.entrees.js

dpz.lang.entrees.js

164 ms

dpz.lang.nutrition.js

dpz.lang.nutrition.js

191 ms

dpz.lang.checkout.js

dpz.lang.checkout.js

349 ms

dpz.lang.builders.js

dpz.lang.builders.js

218 ms

dpz.lang.customer.js

dpz.lang.customer.js

338 ms

dpz.lang.forms.js

dpz.lang.forms.js

224 ms

dpz.lang.coupons.js

dpz.lang.coupons.js

233 ms

dpz.lang.navigation.js

dpz.lang.navigation.js

371 ms

dpz.lang.overlays.js

dpz.lang.overlays.js

227 ms

dpz.easyOrder.js

dpz.easyOrder.js

226 ms

dpz.duc.js

dpz.duc.js

229 ms

dpz.orderTiming.js

dpz.orderTiming.js

230 ms

DPZ_ECOM-79950.js

DPZ_ECOM-79950.js

313 ms

dpz.deliverToMe.js

dpz.deliverToMe.js

159 ms

dpz.utag.constants.js

dpz.utag.constants.js

158 ms

dpz.pbbUpsell.js

dpz.pbbUpsell.js

160 ms

dpz.utag.orderEvents.js

dpz.utag.orderEvents.js

152 ms

tealium-update-all.js

tealium-update-all.js

214 ms

dpz.loyaltyRewards.js

dpz.loyaltyRewards.js

213 ms

dpz.lang.pizzaBuilder.js

dpz.lang.pizzaBuilder.js

214 ms

dpz.geolocation.js

dpz.geolocation.js

246 ms

dpz.oauth.js

dpz.oauth.js

223 ms

dpz.globalPayments.transactionManager.js

dpz.globalPayments.transactionManager.js

214 ms

dpz.couponWizardUpsell.js

dpz.couponWizardUpsell.js

319 ms

dpz.orderStatus.constants.js

dpz.orderStatus.constants.js

223 ms

dpz.lang.stjude.js

dpz.lang.stjude.js

250 ms

DPZ_ECOM-87918.js

DPZ_ECOM-87918.js

321 ms

dpz.loyalty.digitalWallet.js

dpz.loyalty.digitalWallet.js

241 ms

dpz.recentlyAdded.js

dpz.recentlyAdded.js

236 ms

DPZ_ECOM-92800.js

DPZ_ECOM-92800.js

354 ms

dpz.applePay.js

dpz.applePay.js

230 ms

dpz.loyalty.js

dpz.loyalty.js

301 ms

dpz.orderHistory.js

dpz.orderHistory.js

197 ms

dpz.campaignFilters.js

dpz.campaignFilters.js

197 ms

dpz.lang.payment.js

dpz.lang.payment.js

288 ms

dpz.lang.home.js

dpz.lang.home.js

221 ms

dpz.lang.date.js

dpz.lang.date.js

339 ms

dpz.lang.easyOrder.js

dpz.lang.easyOrder.js

312 ms

dpz.customerWallet.js

dpz.customerWallet.js

226 ms

dpz.what3Words.js

dpz.what3Words.js

223 ms

dpz.wow.js

dpz.wow.js

264 ms

dpz.googleMapsStatic.js

dpz.googleMapsStatic.js

293 ms

dpz.lang.loyaltyOffer.js

dpz.lang.loyaltyOffer.js

383 ms

dpz.lang.seo.js

dpz.lang.seo.js

250 ms

ldclient.min.js

ldclient.min.js

326 ms

dpz.mixAndMatch.js

dpz.mixAndMatch.js

311 ms

dpz.weekLongCarryout.js

dpz.weekLongCarryout.js

271 ms

dpz.globalPayments.constants.js

dpz.globalPayments.constants.js

274 ms

dpz.globalPayments.funcs.js

dpz.globalPayments.funcs.js

232 ms

dpz.loyalty.digitalWallet.methods.js

dpz.loyalty.digitalWallet.methods.js

252 ms

gpmACI.js

gpmACI.js

262 ms

dpz.applePayHelper.js

dpz.applePayHelper.js

321 ms

dpz.orderHistory.message.js

dpz.orderHistory.message.js

298 ms

dpz.coupons.js

dpz.coupons.js

232 ms

dpz.mixAndMatch.constants.js

dpz.mixAndMatch.constants.js

247 ms

what3Words.js

what3Words.js

191 ms

eyJjdXN0b20iOnsiY2xpZW50VGltZSI6MTcxNjQyMTkxOTgzMiwiaXNIYW5kaGVsZCI6ZmFsc2UsImlzSHlicmlkIjpmYWxzZSwiaXNLaW9zayI6ZmFsc2UsIm1hcmtldCI6IkRPTUlOSUNBTl9SRVBVQkxJQyIsIm9zTmFtZSI6IldpbmRvd3MiLCJvc1ZlcnNpb24iOiIyMDAwIiwicGxhdGZvcm0iOiJOT0xPIiwic3RvcmVJZCI6IiJ9LCJrZXkiOiI5YzE3OWQxZi1mMDk5LTQxMWYtYTAyZi00YzU2NjkwNjYxNzIifQ

eyJjdXN0b20iOnsiY2xpZW50VGltZSI6MTcxNjQyMTkxOTgzMiwiaXNIYW5kaGVsZCI6ZmFsc2UsImlzSHlicmlkIjpmYWxzZSwiaXNLaW9zayI6ZmFsc2UsIm1hcmtldCI6IkRPTUlOSUNBTl9SRVBVQkxJQyIsIm9zTmFtZSI6IldpbmRvd3MiLCJvc1ZlcnNpb24iOiIyMDAwIiwicGxhdGZvcm0iOiJOT0xPIiwic3RvcmVJZCI6IiJ9LCJrZXkiOiI5YzE3OWQxZi1mMDk5LTQxMWYtYTAyZi00YzU2NjkwNjYxNzIifQ

58 ms

dpz.globalPayments.status.js

dpz.globalPayments.status.js

50 ms

dpz.mixAndMatch.dipsAndTwists.js

dpz.mixAndMatch.dipsAndTwists.js

68 ms

dpz.mixAndMatch.initialize.js

dpz.mixAndMatch.initialize.js

75 ms

dpz.mixAndMatch.methods.js

dpz.mixAndMatch.methods.js

92 ms

dpz.mixAndMatch.serviceMethod.js

dpz.mixAndMatch.serviceMethod.js

49 ms

dpz.mixAndMatch.swapper.js

dpz.mixAndMatch.swapper.js

90 ms

dpz.mixAndMatch.validator.js

dpz.mixAndMatch.validator.js

96 ms

dayjs-locale-es.js

dayjs-locale-es.js

24 ms

dpz.address.js

dpz.address.js

99 ms

Accessibility Review

dominos.com.do accessibility score

100

Accessibility Issues

Best Practices

dominos.com.do best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

dominos.com.do SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dominos.com.do can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Dominos.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.

Social Sharing Optimization

dominos.com.do

Open Graph data is detected on the main page of Domino S. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: