7.3 sec in total
363 ms
6.3 sec
570 ms
Click here to check amazing Toppers content for United States. Otherwise, check out these important facts you probably never knew about toppers.com
Delivery or carry out, late night or right now - Toppers Pizza has you covered. Try our famous Topperstix cheesy bread or one of our specialty pizzas now.
Visit toppers.comWe analyzed Toppers.com page load time and found that the first response time was 363 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
toppers.com performance score
name
value
score
weighting
Value16.2 s
0/100
10%
Value17.4 s
0/100
25%
Value31.3 s
0/100
10%
Value1,300 ms
18/100
30%
Value0.002
100/100
15%
Value25.1 s
1/100
10%
363 ms
290 ms
317 ms
37 ms
25 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 40% of them (37 requests) were addressed to the original Toppers.com, 13% (12 requests) were made to Pixel.mathtag.com and 5% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Toppers.com.
Page size can be reduced by 1.5 MB (39%)
4.0 MB
2.5 MB
In fact, the total size of Toppers.com main page is 4.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. 45% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 42.9 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.9 kB or 76% of the original size.
Potential reduce by 30.2 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. Toppers images are well optimized though.
Potential reduce by 863.0 kB
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 863.0 kB or 63% of the original size.
Potential reduce by 613.0 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. Toppers.com needs all CSS files to be minified and compressed as it can save up to 613.0 kB or 84% of the original size.
Number of requests can be reduced by 57 (67%)
85
28
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Toppers. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
toppers.com
363 ms
css
290 ms
js
317 ms
conversion_async.js
37 ms
WebForms.js
25 ms
BRSIris.min.js
30 ms
BRSIrisCtrlMenuItem.js
31 ms
MicrosoftAjax.js
25 ms
MicrosoftAjaxWebForms.js
30 ms
js
88 ms
ebOneTag.js
68 ms
jquery.rwdImageMaps.min.js
34 ms
conversion.js
41 ms
js
15 ms
analytics.js
141 ms
fbevents.js
171 ms
bat.js
139 ms
i.js
236 ms
Serving
151 ms
bkg-site-header.png
123 ms
Toppers-logo-mobile.png
110 ms
bkg-social-media.jpg
252 ms
bkg-order-cart.png
110 ms
bkg-texture-repeat.jpg
111 ms
Toppers-Pizza.png
109 ms
divider-main-menu.png
121 ms
2017-SMK3-2mediums.jpg
303 ms
toppers-never-settle.jpg
270 ms
toppers-never-settle.png
291 ms
bkg-red-neon.png
760 ms
Staff-Favorites.png
308 ms
bkg-white-fray.jpg
261 ms
LG2T%20Single.jpg
271 ms
topperstix-3cheese[2].jpg
2040 ms
dropdown-white-small.png
273 ms
lg2t-triple.jpg
277 ms
social-section-mobile.jpg
470 ms
social-block.jpg
471 ms
bkg-texture.jpg
498 ms
za-crew.jpg
489 ms
best-franchise.jpg
763 ms
bkg-main-content.png
403 ms
bkg-site-footer-bigger.jpg
408 ms
never-settle.png
416 ms
delivery.png
427 ms
RobotoCondensed-Bold-webfont.woff
618 ms
DroidSans-webfont.woff
5348 ms
fontello.woff
633 ms
peixefrito-t.woff
803 ms
iframe
45 ms
52 ms
linkid.js
11 ms
ecommerce.js
12 ms
img
36 ms
img
34 ms
collect
2 ms
collect
56 ms
46 ms
981538248535815
29 ms
18 ms
18 ms
js
25 ms
img
107 ms
img
14 ms
pixel
37 ms
img
38 ms
pixel
14 ms
img
15 ms
cksync.php
203 ms
Pug
134 ms
334886.png
125 ms
vendormm.gif
161 ms
sync
118 ms
cs
719 ms
743 ms
match
118 ms
img
64 ms
img
83 ms
img
92 ms
img
76 ms
tap.php
17 ms
sd
16 ms
rum
21 ms
match
11 ms
img
27 ms
img
47 ms
pixel.gif
25 ms
4448
147 ms
2948
129 ms
trpx.gif
87 ms
match
68 ms
nr-1044.min.js
36 ms
collect
2 ms
toppers.com accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
toppers.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
Registers an unload listener
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
toppers.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Toppers.com 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 Toppers.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.
toppers.com
Open Graph description is not detected on the main page of Toppers. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: