2 sec in total
165 ms
1.7 sec
68 ms
Click here to check amazing Domino S content for Ecuador. Otherwise, check out these important facts you probably never knew about dominos.ec
Order pizza, sandwiches & more online for carryout or delivery from Domino's. View menu, find locations, track orders. Sign up for Domino's email & text offers to get great deals on your next order.
Visit dominos.ecWe analyzed Dominos.ec page load time and found that the first response time was 165 ms and then it took 1.8 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.
dominos.ec performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value17.0 s
0/100
25%
Value8.4 s
19/100
10%
Value2,180 ms
6/100
30%
Value0.411
24/100
15%
Value23.6 s
1/100
10%
165 ms
65 ms
91 ms
61 ms
119 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Dominos.ec, 94% (101 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 (546 ms) relates to the external source Cache.dominos.com.
Page size can be reduced by 5.9 MB (73%)
8.1 MB
2.2 MB
In fact, the total size of Dominos.ec main page is 8.1 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. 55% of websites need less resources to load. Javascripts take 7.3 MB which makes up the majority of the site volume.
Potential reduce by 42.4 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.4 kB or 73% of the original size.
Potential reduce by 5.3 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 5.3 MB or 73% of the original size.
Potential reduce by 574.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.ec needs all CSS files to be minified and compressed as it can save up to 574.9 kB or 78% of the original size.
Number of requests can be reduced by 102 (96%)
106
4
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.
www.dominos.ec
165 ms
screen.css
65 ms
screen.desktop.css
91 ms
screen.fixed.css
61 ms
homepage.css
119 ms
homepage.desktop.css
85 ms
homepage.fixed.css
88 ms
override.min.css
92 ms
xdomain.js
45 ms
core-js-bundle.js
250 ms
bootlibs.js
94 ms
dpz.roloRedirect.js
91 ms
boot.js
97 ms
base-site.js
157 ms
home-site.js
92 ms
scripts.js
160 ms
raygun.min.js
27 ms
4KTV2-QRXXN-6JH3L-VGPDD-BJ5DR
29 ms
config.json
420 ms
dpz.easyOrder.js
466 ms
dayjs.min.js
175 ms
customParseFormat.js
174 ms
advancedFormat.js
135 ms
updateLocale.js
133 ms
dpz.marketConfig.js
133 ms
dpz.lang.general.js
137 ms
dpz.lang.builders.js
135 ms
dpz.lang.navigation.js
133 ms
dpz.lang.payment.js
133 ms
config.js
135 ms
ua-parser.min.js
134 ms
dpz.createCanonical.js
209 ms
dpz.couponServiceMethodWarning.js
171 ms
dpz.oauth.constants.js
170 ms
dpz.lang.errors.js
215 ms
dpz.lang.confirmation.js
329 ms
dpz.seo.js
176 ms
dpz.lang.titles.js
226 ms
dpz.storeVariance.js
183 ms
dpz.orderCapacity.js
194 ms
dpz.hotspots.js
215 ms
dpz.serviceMethod.constants.js
218 ms
dpz.thresholdCoupons.js
244 ms
constants.js
218 ms
dpz.lang.errorsValidator.js
283 ms
dpz.lang.locations.js
259 ms
dpz.lang.entrees.js
256 ms
dpz.lang.nutrition.js
314 ms
dpz.lang.checkout.js
293 ms
dpz.lang.customer.js
267 ms
dpz.lang.forms.js
365 ms
dpz.lang.coupons.js
378 ms
dpz.lang.overlays.js
361 ms
dpz.duc.js
396 ms
dpz.orderTiming.js
489 ms
DPZ_ECOM-69775.js
254 ms
DPZ_ECOM-79950.js
301 ms
DPZ_ECOM-86052.js
546 ms
dpz.deliverToMe.js
271 ms
dpz.utag.constants.js
283 ms
dpz.utag.orderEvents.js
285 ms
tealium-update-all.js
284 ms
dpz.loyaltyRewards.js
293 ms
dpz.lang.pizzaBuilder.js
335 ms
dpz.geolocation.js
306 ms
dpz.oauth.js
278 ms
dpz.globalPayments.transactionManager.js
283 ms
dpz.couponWizardUpsell.js
291 ms
dpz.orderStatus.constants.js
310 ms
dpz.lang.stjude.js
412 ms
dpz.loyalty.digitalWallet.js
286 ms
dpz.recentlyAdded.js
394 ms
dpz.mixAndMatch.js
381 ms
dpz.weekLongCarryout.js
273 ms
dpz.applePay.js
281 ms
dpz.loyalty.js
373 ms
dpz.orderHistory.js
367 ms
dpz.campaignFilters.js
346 ms
dpz.lang.home.js
375 ms
dpz.lang.date.js
328 ms
dpz.lang.easyOrder.js
353 ms
dpz.customerWallet.js
311 ms
dpz.what3Words.js
299 ms
dpz.wow.js
279 ms
dpz.googleMapsStatic.js
305 ms
dpz.lang.loyaltyOffer.js
312 ms
ldclient.min.js
283 ms
dpz.lang.seo.js
315 ms
dpz.globalPayments.constants.js
244 ms
dpz.globalPayments.funcs.js
235 ms
dpz.loyalty.digitalWallet.methods.js
329 ms
dpz.coupons.js
190 ms
gpmACI.js
96 ms
dpz.applePayHelper.js
189 ms
dpz.orderHistory.message.js
85 ms
dpz.mixAndMatch.constants.js
175 ms
dpz.mixAndMatch.dipsAndTwists.js
93 ms
dpz.mixAndMatch.initialize.js
104 ms
dpz.mixAndMatch.methods.js
87 ms
dpz.mixAndMatch.serviceMethod.js
161 ms
dpz.mixAndMatch.swapper.js
139 ms
dpz.mixAndMatch.validator.js
381 ms
what3Words.js
214 ms
eyJjdXN0b20iOnsiY2xpZW50VGltZSI6MTcwNjIwNDYzODA0MywiaXNIYW5kaGVsZCI6ZmFsc2UsImlzSHlicmlkIjpmYWxzZSwiaXNLaW9zayI6ZmFsc2UsIm1hcmtldCI6IkVDVUFET1IiLCJvc05hbWUiOiJMaW51eCIsIm9zVmVyc2lvbiI6Imk2ODYiLCJwbGF0Zm9ybSI6Ik5PTE8iLCJzdG9yZUlkIjoiIn0sImtleSI6IjBmZDNiOTQ4LWM5Y2QtNDlmMy1hNzlhLWIxYmM1NDIwOWUyNSJ9
46 ms
dpz.globalPayments.status.js
219 ms
dayjs-locale-es.js
193 ms
dpz.address.js
156 ms
dominos.ec 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.
dominos.ec 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
Missing source maps for large first-party JavaScript
dominos.ec 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
EN
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dominos.ec can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Dominos.ec 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.
dominos.ec
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: