Tools & Wizards About Us
dominos.no screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

dominos.no

Dominos Pizza | World leader in home delivery of pizza

Page Load Speed

2.9 sec in total

First Response

387 ms

Resources Loaded

2.2 sec

Page Rendered

359 ms

dominos.no screenshot

About Website

Visit dominos.no now to see the best up-to-date Dominos content for Norway and also check out these interesting facts you probably never knew about dominos.no

Discover exclusive Domino's offers. The easiest and fastest way to order your favorite pizza online.

Visit dominos.no

Key Findings

We analyzed Dominos.no page load time and found that the first response time was 387 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

dominos.no performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value5,650 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

dominos.no

387 ms

www.dominos.no

801 ms

en

226 ms

cacc180fd6ebc560.css

112 ms

73e3b0436e171226.css

221 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 71% of them (17 requests) were addressed to the original Dominos.no, 29% (7 requests) were made to Cdn.sanity.io. The less responsive or slowest element that took the longest time to load (801 ms) belongs to the original domain Dominos.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 81.6 kB (11%)

Content Size

767.5 kB

After Optimization

685.9 kB

  • HTML
  • Images

In fact, the total size of Dominos.no main page is 767.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 657.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 78.6 kB

  • Original 110.4 kB
  • After minification 110.4 kB
  • After compression 31.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 78.6 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 3.0 kB

  • Original 657.1 kB
  • After minification 654.1 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Dominos images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 11 (52%)

Requests Now

21

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dominos.no

dominos.no

387 ms

www.dominos.no

www.dominos.no

801 ms

en

en

226 ms

cacc180fd6ebc560.css

cacc180fd6ebc560.css

112 ms

73e3b0436e171226.css

73e3b0436e171226.css

221 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

424 ms

webpack-aa349c54407f5ec2.js

webpack-aa349c54407f5ec2.js

313 ms

framework-79bce4a3a540b080.js

framework-79bce4a3a540b080.js

460 ms

main-f8215d445a10db0f.js

main-f8215d445a10db0f.js

444 ms

_app-6c9be0cb048018bb.js

_app-6c9be0cb048018bb.js

744 ms

8100-cc135ff53606d25f.js

8100-cc135ff53606d25f.js

374 ms

9924-f600a9f67f3e88c1.js

9924-f600a9f67f3e88c1.js

420 ms

8967-310d11f06e65c8a0.js

8967-310d11f06e65c8a0.js

495 ms

index-3b6dbfb6165a1116.js

index-3b6dbfb6165a1116.js

530 ms

_buildManifest.js

_buildManifest.js

528 ms

_ssgManifest.js

_ssgManifest.js

533 ms

_middlewareManifest.js

_middlewareManifest.js

564 ms

5b6c9154f9072fa856f6a840e0bea4d198c637c9-189x40.svg

5b6c9154f9072fa856f6a840e0bea4d198c637c9-189x40.svg

234 ms

f56a008a160d1c15ef154591ddb631fa7bb07d52-2038x978.jpg

f56a008a160d1c15ef154591ddb631fa7bb07d52-2038x978.jpg

363 ms

c1936758defbcf4960ed22116acfd9811131bcb8-867x256.png

c1936758defbcf4960ed22116acfd9811131bcb8-867x256.png

276 ms

c4814119caff78a07e4529011acc0286ab3330d2-821x256.png

c4814119caff78a07e4529011acc0286ab3330d2-821x256.png

287 ms

68ec32982d369bb8ff93fa886578d0daeaffbd41-2320x2170.png

68ec32982d369bb8ff93fa886578d0daeaffbd41-2320x2170.png

491 ms

fb7b338d2f7f6962e516623e0b7f6292e64399d7-1160x1248.png

fb7b338d2f7f6962e516623e0b7f6292e64399d7-1160x1248.png

493 ms

1890b5ae2705692a6a60a1b04ceafd96da455459-1160x1088.png

1890b5ae2705692a6a60a1b04ceafd96da455459-1160x1088.png

441 ms

Accessibility Review

dominos.no accessibility score

77

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-*] attributes do not have valid values

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

Best Practices

dominos.no best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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.no SEO score

85

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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