3.2 sec in total
360 ms
2.8 sec
54 ms
Click here to check amazing Domino S content for Egypt. Otherwise, check out these important facts you probably never knew about dominos.com.eg
Order pizza & 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.com.egWe analyzed Dominos.com.eg page load time and found that the first response time was 360 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
dominos.com.eg performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value18.1 s
0/100
25%
Value10.4 s
8/100
10%
Value1,510 ms
14/100
30%
Value0.214
58/100
15%
Value27.4 s
0/100
10%
360 ms
198 ms
186 ms
193 ms
217 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.com.eg, 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 (1 sec) relates to the external source Cache.dominos.com.
Page size can be reduced by 5.5 MB (74%)
7.4 MB
1.9 MB
In fact, the total size of Dominos.com.eg main page is 7.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. 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. Javascripts take 6.7 MB which makes up the majority of the site volume.
Potential reduce by 42.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.8 kB or 73% of the original size.
Potential reduce by 4.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.9 MB or 74% of the original size.
Potential reduce by 515.7 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.eg needs all CSS files to be minified and compressed as it can save up to 515.7 kB or 75% of the original size.
Number of requests can be reduced by 100 (96%)
104
4
The browser has sent 104 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 95 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.dominos.com.eg
360 ms
screen.css
198 ms
screen.desktop.css
186 ms
screen.fixed.css
193 ms
homepage.css
217 ms
homepage.desktop.css
150 ms
homepage.fixed.css
231 ms
override.min.css
457 ms
xdomain.js
38 ms
core-js-bundle.js
238 ms
bootlibs.js
244 ms
dpz.roloRedirect.js
409 ms
boot.js
254 ms
base-site.js
236 ms
home-site.js
266 ms
scripts.js
282 ms
raygun.min.js
253 ms
MWPRJ-HHUCT-BWJFR-B46N7-E37VS
260 ms
pizzapressar-fill-webfont.woff
151 ms
OneDotCd-Bold.woff
181 ms
dayjs.min.js
159 ms
customParseFormat.js
129 ms
advancedFormat.js
178 ms
updateLocale.js
180 ms
dpz.marketConfig.js
290 ms
dpz.masterKillConfig.js
185 ms
ua-parser.min.js
305 ms
dpz.createCanonical.js
223 ms
dpz.couponServiceMethodWarning.js
246 ms
dpz.oauth.constants.js
219 ms
dpz.lang.errors.js
350 ms
dpz.lang.confirmation.js
346 ms
dpz.seo.js
258 ms
dpz.lang.titles.js
376 ms
dpz.storeVariance.js
294 ms
dpz.orderCapacity.js
325 ms
dpz.hotspots.js
335 ms
dpz.serviceMethod.constants.js
429 ms
dpz.thresholdCoupons.js
370 ms
constants.js
418 ms
dpz.lang.errorsValidator.js
488 ms
dpz.lang.locations.js
484 ms
dpz.lang.general.js
488 ms
dpz.lang.entrees.js
494 ms
dpz.lang.nutrition.js
542 ms
dpz.lang.checkout.js
544 ms
dpz.lang.builders.js
594 ms
dpz.lang.customer.js
621 ms
dpz.lang.forms.js
590 ms
dpz.lang.coupons.js
609 ms
dpz.lang.navigation.js
636 ms
dpz.lang.overlays.js
743 ms
dpz.easyOrder.js
631 ms
dpz.duc.js
692 ms
config.json
47 ms
dpz.orderTiming.js
541 ms
dpz.deliverToMe.js
562 ms
dpz.utag.constants.js
591 ms
dpz.pbbUpsell.js
523 ms
dpz.utag.orderEvents.js
546 ms
tealium-update-all.js
585 ms
dpz.loyaltyRewards.js
563 ms
dpz.lang.pizzaBuilder.js
1008 ms
dpz.geolocation.js
542 ms
dpz.oauth.js
571 ms
dpz.globalPayments.transactionManager.js
551 ms
dpz.couponWizardUpsell.js
519 ms
dpz.orderStatus.constants.js
506 ms
dpz.lang.stjude.js
826 ms
dpz.loyalty.digitalWallet.js
515 ms
dpz.mixAndMatch.constants.js
516 ms
dpz.mixAndMatch.methods.js
602 ms
dpz.recentlyAdded.js
498 ms
dpz.applePay.js
509 ms
DPZ_ECOM-97921.js
573 ms
dpz.loyalty.js
538 ms
dpz.orderHistory.js
519 ms
dpz.campaignFilters.js
462 ms
dpz.lang.payment.js
648 ms
dpz.lang.home.js
814 ms
dpz.lang.date.js
575 ms
dpz.lang.easyOrder.js
846 ms
dpz.customerWallet.js
560 ms
dpz.what3Words.js
559 ms
dpz.wow.js
570 ms
dpz.googleMapsStatic.js
606 ms
dpz.lang.loyaltyOffer.js
641 ms
dpz.lang.seo.js
955 ms
ldclient.min.js
617 ms
dpz.mixAndMatch.js
577 ms
dpz.weekLongCarryout.js
614 ms
dpz.coupons.virtual.js
545 ms
dpz.globalPayments.constants.js
499 ms
dpz.globalPayments.funcs.js
534 ms
dpz.loyalty.digitalWallet.methods.js
571 ms
dpz.coupons.js
507 ms
gpmACI.js
441 ms
dpz.applePayHelper.js
492 ms
dpz.couponSwapper.js
456 ms
dpz.orderHistory.message.js
474 ms
what3Words.js
294 ms
dpz.mixAndMatch.dipsAndTwists.js
189 ms
dpz.mixAndMatch.initialize.js
180 ms
dpz.mixAndMatch.validator.js
209 ms
eyJjdXN0b20iOnsiY2xpZW50VGltZSI6MTcyNTE3NzMwNTc2MCwiaXNIYW5kaGVsZCI6ZmFsc2UsImlzSHlicmlkIjpmYWxzZSwiaXNLaW9zayI6ZmFsc2UsIm1hcmtldCI6IkVHWVBUIiwib3NOYW1lIjoiZ2VudG9vIiwib3NWZXJzaW9uIjoicjYiLCJwbGF0Zm9ybSI6Ik5PTE8iLCJzdG9yZUlkIjoiIn0sImtleSI6ImJhMDZiZTkyLTk5ZTAtNDg4NS1iZTI0LWFlOTZhNWZmYWMwOCJ9
40 ms
dayjs-locale-ar.js
162 ms
dpz.globalPayments.status.js
97 ms
dominos.com.eg accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
dominos.com.eg 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
dominos.com.eg SEO score
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
AR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dominos.com.eg 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 Arabic language. Our system also found out that Dominos.com.eg 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.com.eg
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: