1.7 sec in total
129 ms
1.5 sec
53 ms
Welcome to dominospanama.com homepage info - get ready to check Dominos Panama best content for Panama right away, or after learning these important things about dominospanama.com
Pide Domino's en linea para domicilio o recoger en tienda. Tenemos deliciosas pizzas, acompañamientos, bebidas y postres. Pide ahora!
Visit dominospanama.comWe analyzed Dominospanama.com page load time and found that the first response time was 129 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.
dominospanama.com performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value15.7 s
0/100
25%
Value8.3 s
19/100
10%
Value2,620 ms
4/100
30%
Value0.838
4/100
15%
Value23.2 s
1/100
10%
129 ms
107 ms
100 ms
147 ms
155 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 Dominospanama.com, 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 (595 ms) relates to the external source Cache.dominos.com.
Page size can be reduced by 3.5 MB (64%)
5.4 MB
1.9 MB
In fact, the total size of Dominospanama.com main page is 5.4 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.8 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 3.0 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.
Potential reduce by 446.2 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. Dominospanama.com needs all CSS files to be minified and compressed as it can save up to 446.2 kB or 74% 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 Dominos Panama. 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.dominospanama.com
129 ms
screen.css
107 ms
screen.desktop.css
100 ms
screen.fixed.css
147 ms
homepage.css
155 ms
homepage.desktop.css
142 ms
homepage.fixed.css
145 ms
override.min.css
153 ms
xdomain.js
194 ms
core-js-bundle.js
150 ms
bootlibs.js
150 ms
dpz.roloRedirect.js
152 ms
boot.js
295 ms
base-site.js
318 ms
home-site.js
293 ms
scripts.js
412 ms
raygun.min.js
300 ms
4KTV2-QRXXN-6JH3L-VGPDD-BJ5DR
305 ms
dayjs.min.js
114 ms
customParseFormat.js
111 ms
advancedFormat.js
113 ms
updateLocale.js
118 ms
dpz.marketConfig.js
149 ms
dpz.masterKillConfig.js
109 ms
ua-parser.min.js
109 ms
dpz.createCanonical.js
149 ms
dpz.couponServiceMethodWarning.js
110 ms
dpz.oauth.constants.js
113 ms
dpz.lang.errors.js
105 ms
dpz.lang.confirmation.js
139 ms
dpz.seo.js
106 ms
dpz.lang.titles.js
154 ms
dpz.storeVariance.js
106 ms
dpz.orderCapacity.js
107 ms
dpz.hotspots.js
107 ms
dpz.serviceMethod.constants.js
107 ms
dpz.thresholdCoupons.js
137 ms
constants.js
140 ms
dpz.lang.errorsValidator.js
199 ms
dpz.lang.locations.js
140 ms
dpz.lang.general.js
155 ms
dpz.lang.entrees.js
138 ms
dpz.lang.nutrition.js
163 ms
dpz.lang.checkout.js
153 ms
dpz.lang.builders.js
150 ms
dpz.lang.customer.js
327 ms
dpz.lang.forms.js
160 ms
dpz.lang.coupons.js
195 ms
dpz.lang.navigation.js
164 ms
dpz.lang.overlays.js
206 ms
dpz.easyOrder.js
250 ms
dpz.duc.js
399 ms
dpz.orderTiming.js
329 ms
DPZ_ECOM-79950.js
166 ms
dpz.deliverToMe.js
196 ms
dpz.utag.constants.js
282 ms
dpz.pbbUpsell.js
482 ms
dpz.utag.orderEvents.js
215 ms
tealium-update-all.js
298 ms
dpz.loyaltyRewards.js
248 ms
dpz.lang.pizzaBuilder.js
295 ms
dpz.geolocation.js
286 ms
dpz.oauth.js
415 ms
dpz.globalPayments.transactionManager.js
482 ms
dpz.couponWizardUpsell.js
408 ms
dpz.orderStatus.constants.js
295 ms
dpz.lang.stjude.js
302 ms
dpz.loyalty.digitalWallet.js
315 ms
dpz.mixAndMatch.constants.js
378 ms
config.json
39 ms
dpz.mixAndMatch.methods.js
292 ms
dpz.recentlyAdded.js
294 ms
DPZ_ECOM-92800.js
297 ms
dpz.applePay.js
301 ms
DPZ_ECOM-97921.js
372 ms
dpz.loyalty.js
362 ms
dpz.orderHistory.js
362 ms
dpz.campaignFilters.js
361 ms
dpz.lang.payment.js
451 ms
dpz.lang.home.js
432 ms
dpz.lang.date.js
366 ms
dpz.lang.easyOrder.js
595 ms
dpz.customerWallet.js
394 ms
dpz.what3Words.js
414 ms
dpz.wow.js
528 ms
dpz.googleMapsStatic.js
425 ms
dpz.lang.loyaltyOffer.js
386 ms
dpz.lang.seo.js
469 ms
ldclient.min.js
356 ms
dpz.loyalty.digitalWallet.methods.js
276 ms
dpz.couponSwapper.js
214 ms
dpz.coupons.js
245 ms
gpmACI.js
211 ms
dpz.applePayHelper.js
228 ms
dpz.orderHistory.message.js
243 ms
dpz.coupons.virtual.js
220 ms
dpz.mixAndMatch.js
145 ms
dpz.weekLongCarryout.js
193 ms
dpz.globalPayments.constants.js
235 ms
dpz.globalPayments.funcs.js
236 ms
what3Words.js
223 ms
eyJjdXN0b20iOnsiY2xpZW50VGltZSI6MTcxOTc5MzE4ODE5OSwiaXNIYW5kaGVsZCI6ZmFsc2UsImlzSHlicmlkIjpmYWxzZSwiaXNLaW9zayI6ZmFsc2UsIm1hcmtldCI6IlBBTkFNQSIsIm9zTmFtZSI6IldpbmRvd3MiLCJvc1ZlcnNpb24iOiJYUCIsInBsYXRmb3JtIjoiTk9MTyIsInN0b3JlSWQiOiIifSwia2V5IjoiYjAwMzRhZjQtZWVhNi00NWJlLTgyYmItZDYxNGEyNDE4MDVkIn0
62 ms
dpz.globalPayments.status.js
73 ms
dpz.mixAndMatch.dipsAndTwists.js
48 ms
dpz.mixAndMatch.initialize.js
123 ms
dpz.mixAndMatch.validator.js
85 ms
dayjs-locale-es.js
72 ms
dominospanama.com accessibility score
dominospanama.com 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
dominospanama.com 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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dominospanama.com 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 Dominospanama.com 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.
dominospanama.com
Open Graph data is detected on the main page of Dominos Panama. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: