Tools & Wizards About Us
dominos.com.co screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

dominos.com.co

Domino’s Pizza - Pide a tu domicilio o recógelo en nuestra tienda

Page Load Speed

1.7 sec in total

First Response

58 ms

Resources Loaded

1.6 sec

Page Rendered

57 ms

dominos.com.co screenshot

About Website

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

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

Visit dominos.com.co

Key Findings

We analyzed Dominos.com.co page load time and found that the first response time was 58 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.co performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value3,070 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value28.5 s

0/100

10%

Network Requests Diagram

www.dominos.com.co

58 ms

screen.css

195 ms

screen.desktop.css

186 ms

screen.fixed.css

158 ms

homepage.css

170 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Dominos.com.co, 94% (103 requests) were made to Cache.dominos.com and 1% (1 request) were made to S.go-mpulse.net. The less responsive or slowest element that took the longest time to load (412 ms) relates to the external source Cache.dominos.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.9 MB (70%)

Content Size

7.0 MB

After Optimization

2.1 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Dominos.com.co main page is 7.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. 70% of websites need less resources to load. Javascripts take 6.7 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 44.5 kB

  • Original 60.8 kB
  • After minification 58.8 kB
  • After compression 16.2 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 44.5 kB or 73% of the original size.

JavaScript Optimization

-72%

Potential reduce by 4.8 MB

  • Original 6.7 MB
  • After minification 6.7 MB
  • After compression 1.9 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 4.8 MB or 72% of the original size.

CSS Optimization

-32%

Potential reduce by 69.4 kB

  • Original 216.9 kB
  • After minification 216.9 kB
  • After compression 147.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. Dominos.com.co needs all CSS files to be minified and compressed as it can save up to 69.4 kB or 32% of the original size.

Requests Breakdown

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

Requests Now

106

After Optimization

4

  • AJAX
  • JavaScript
  • CSS

The browser has sent 106 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 97 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.co

www.dominos.com.co

58 ms

screen.css

screen.css

195 ms

screen.desktop.css

screen.desktop.css

186 ms

screen.fixed.css

screen.fixed.css

158 ms

homepage.css

homepage.css

170 ms

homepage.desktop.css

homepage.desktop.css

154 ms

homepage.fixed.css

homepage.fixed.css

188 ms

override.min.css

override.min.css

336 ms

xdomain.js

xdomain.js

183 ms

core-js-bundle.js

core-js-bundle.js

168 ms

bootlibs.js

bootlibs.js

217 ms

dpz.roloRedirect.js

dpz.roloRedirect.js

186 ms

boot.js

boot.js

215 ms

base-site.js

base-site.js

259 ms

home-site.js

home-site.js

188 ms

scripts.js

scripts.js

231 ms

raygun.min.js

raygun.min.js

276 ms

4KTV2-QRXXN-6JH3L-VGPDD-BJ5DR

4KTV2-QRXXN-6JH3L-VGPDD-BJ5DR

275 ms

OneDot.woff

OneDot.woff

261 ms

OneDot-Bold.woff

OneDot-Bold.woff

261 ms

dpz.hotspots.js

dpz.hotspots.js

82 ms

dayjs.min.js

dayjs.min.js

82 ms

customParseFormat.js

customParseFormat.js

184 ms

advancedFormat.js

advancedFormat.js

84 ms

updateLocale.js

updateLocale.js

85 ms

dpz.marketConfig.js

dpz.marketConfig.js

137 ms

dpz.lang.general.js

dpz.lang.general.js

81 ms

dpz.lang.builders.js

dpz.lang.builders.js

138 ms

dpz.lang.navigation.js

dpz.lang.navigation.js

135 ms

dpz.lang.payment.js

dpz.lang.payment.js

82 ms

config.js

config.js

81 ms

ua-parser.min.js

ua-parser.min.js

267 ms

dpz.utag.orderEvents.js

dpz.utag.orderEvents.js

178 ms

dpz.createCanonical.js

dpz.createCanonical.js

138 ms

tealium-update-all.js

tealium-update-all.js

135 ms

dpz.easyOrder.js

dpz.easyOrder.js

56 ms

dpz.couponServiceMethodWarning.js

dpz.couponServiceMethodWarning.js

57 ms

dpz.oauth.constants.js

dpz.oauth.constants.js

58 ms

dpz.lang.errors.js

dpz.lang.errors.js

56 ms

dpz.lang.confirmation.js

dpz.lang.confirmation.js

161 ms

dpz.seo.js

dpz.seo.js

56 ms

dpz.lang.titles.js

dpz.lang.titles.js

88 ms

dpz.storeVariance.js

dpz.storeVariance.js

57 ms

dpz.orderCapacity.js

dpz.orderCapacity.js

95 ms

dpz.serviceMethod.constants.js

dpz.serviceMethod.constants.js

89 ms

dpz.thresholdCoupons.js

dpz.thresholdCoupons.js

94 ms

constants.js

constants.js

135 ms

dpz.lang.errorsValidator.js

dpz.lang.errorsValidator.js

122 ms

dpz.lang.locations.js

dpz.lang.locations.js

412 ms

dpz.lang.entrees.js

dpz.lang.entrees.js

109 ms

dpz.lang.nutrition.js

dpz.lang.nutrition.js

146 ms

dpz.lang.checkout.js

dpz.lang.checkout.js

251 ms

dpz.lang.customer.js

dpz.lang.customer.js

183 ms

dpz.lang.forms.js

dpz.lang.forms.js

220 ms

dpz.lang.coupons.js

dpz.lang.coupons.js

170 ms

dpz.duc.js

dpz.duc.js

187 ms

dpz.orderTiming.js

dpz.orderTiming.js

182 ms

DPZ_ECOM-69775.js

DPZ_ECOM-69775.js

297 ms

dpz.deliverToMe.js

dpz.deliverToMe.js

194 ms

dpz.utag.constants.js

dpz.utag.constants.js

242 ms

dpz.lang.pizzaBuilder.js

dpz.lang.pizzaBuilder.js

231 ms

dpz.geolocation.js

dpz.geolocation.js

232 ms

dpz.globalPayments.transactionManager.js

dpz.globalPayments.transactionManager.js

245 ms

dpz.couponWizardUpsell.js

dpz.couponWizardUpsell.js

213 ms

dpz.lang.stjude.js

dpz.lang.stjude.js

238 ms

dpz.loyalty.digitalWallet.js

dpz.loyalty.digitalWallet.js

211 ms

DPZ_ECOM-73139.js

DPZ_ECOM-73139.js

212 ms

dpz.recentlyAdded.js

dpz.recentlyAdded.js

246 ms

dpz.mixAndMatch.js

dpz.mixAndMatch.js

215 ms

dpz.weekLongCarryout.js

dpz.weekLongCarryout.js

334 ms

config.json

config.json

76 ms

dpz.applePay.js

dpz.applePay.js

248 ms

dpz.loyalty.js

dpz.loyalty.js

363 ms

dpz.orderHistory.js

dpz.orderHistory.js

330 ms

dpz.lang.home.js

dpz.lang.home.js

318 ms

dpz.lang.date.js

dpz.lang.date.js

299 ms

dpz.lang.easyOrder.js

dpz.lang.easyOrder.js

297 ms

dpz.customerWallet.js

dpz.customerWallet.js

328 ms

dpz.what3Words.js

dpz.what3Words.js

388 ms

dpz.wow.js

dpz.wow.js

303 ms

dpz.googleMapsStatic.js

dpz.googleMapsStatic.js

308 ms

dpz.lang.loyaltyOffer.js

dpz.lang.loyaltyOffer.js

332 ms

dpz.lang.overlays.js

dpz.lang.overlays.js

327 ms

dpz.lang.seo.js

dpz.lang.seo.js

351 ms

ldclient.min.js

ldclient.min.js

266 ms

dpz.globalPayments.constants.js

dpz.globalPayments.constants.js

349 ms

dpz.globalPayments.funcs.js

dpz.globalPayments.funcs.js

227 ms

dpz.loyalty.digitalWallet.methods.js

dpz.loyalty.digitalWallet.methods.js

295 ms

DPZ_ECOM-67857.js

DPZ_ECOM-67857.js

259 ms

dpz.mixAndMatch.constants.js

dpz.mixAndMatch.constants.js

300 ms

dpz.mixAndMatch.dipsAndTwists.js

dpz.mixAndMatch.dipsAndTwists.js

287 ms

dpz.mixAndMatch.initialize.js

dpz.mixAndMatch.initialize.js

288 ms

dpz.mixAndMatch.methods.js

dpz.mixAndMatch.methods.js

299 ms

dpz.mixAndMatch.serviceMethod.js

dpz.mixAndMatch.serviceMethod.js

325 ms

dpz.mixAndMatch.swapper.js

dpz.mixAndMatch.swapper.js

324 ms

dpz.mixAndMatch.validator.js

dpz.mixAndMatch.validator.js

394 ms

gpmACI.js

gpmACI.js

233 ms

dpz.applePayHelper.js

dpz.applePayHelper.js

248 ms

dpz.coupons.js

dpz.coupons.js

243 ms

dpz.orderHistory.message.js

dpz.orderHistory.message.js

214 ms

what3Words.js

what3Words.js

138 ms

eyJjdXN0b20iOnsiY2xpZW50VGltZSI6MTcxODE3MjM5NzgyMSwiaXNIYW5kaGVsZCI6ZmFsc2UsImlzSHlicmlkIjpmYWxzZSwiaXNLaW9zayI6ZmFsc2UsIm1hcmtldCI6IkNPTE9NQklBIiwib3NOYW1lIjoiV2luZG93cyIsIm9zVmVyc2lvbiI6IjIwMDAiLCJwbGF0Zm9ybSI6Ik5PTE8iLCJzdG9yZUlkIjoiIn0sImtleSI6IjUyMTdmYjVhLWMyNmEtNDlmYi04MzkxLTc2YTU3NTdkNGJhZSJ9

eyJjdXN0b20iOnsiY2xpZW50VGltZSI6MTcxODE3MjM5NzgyMSwiaXNIYW5kaGVsZCI6ZmFsc2UsImlzSHlicmlkIjpmYWxzZSwiaXNLaW9zayI6ZmFsc2UsIm1hcmtldCI6IkNPTE9NQklBIiwib3NOYW1lIjoiV2luZG93cyIsIm9zVmVyc2lvbiI6IjIwMDAiLCJwbGF0Zm9ybSI6Ik5PTE8iLCJzdG9yZUlkIjoiIn0sImtleSI6IjUyMTdmYjVhLWMyNmEtNDlmYi04MzkxLTc2YTU3NTdkNGJhZSJ9

51 ms

analyticSearchStore.js

analyticSearchStore.js

140 ms

addCombotizala.js

addCombotizala.js

116 ms

gettingLastAddress.js

gettingLastAddress.js

117 ms

dayjs-locale-es.js

dayjs-locale-es.js

115 ms

sdk.min.js

sdk.min.js

32 ms

dpz.address.js

dpz.address.js

131 ms

dpz.globalPayments.status.js

dpz.globalPayments.status.js

116 ms

Accessibility Review

dominos.com.co accessibility score

100

Accessibility Issues

Best Practices

dominos.com.co best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

dominos.com.co 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

    N/A

  • 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.co 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 Spanish. Our system also found out that Dominos.com.co 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.co

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: