Tools & Wizards About Us
myquiznos.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

myquiznos.com

Something went wrong

Page Load Speed

1.6 sec in total

First Response

331 ms

Resources Loaded

1.1 sec

Page Rendered

124 ms

myquiznos.com screenshot

About Website

Welcome to myquiznos.com homepage info - get ready to check Myquiznos best content for United States right away, or after learning these important things about myquiznos.com

Visit myquiznos.com

Key Findings

We analyzed Myquiznos.com page load time and found that the first response time was 331 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

myquiznos.com performance score

0

Network Requests Diagram

myquiznos.com

331 ms

myquiznos.com

252 ms

Login.aspx

136 ms

main.css

91 ms

Window.css

151 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 90% of them (19 requests) were addressed to the original Myquiznos.com, 10% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (331 ms) belongs to the original domain Myquiznos.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 424.1 kB (81%)

Content Size

521.9 kB

After Optimization

97.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Myquiznos.com main page is 521.9 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. 25% of websites need less resources to load. Javascripts take 476.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 14.1 kB

  • Original 19.5 kB
  • After minification 17.3 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 2.2 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 14.1 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 20 B

  • Original 5.1 kB
  • After minification 5.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. Myquiznos images are well optimized though.

JavaScript Optimization

-82%

Potential reduce by 392.5 kB

  • Original 476.5 kB
  • After minification 345.2 kB
  • After compression 84.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 392.5 kB or 82% of the original size.

CSS Optimization

-84%

Potential reduce by 17.5 kB

  • Original 20.7 kB
  • After minification 14.6 kB
  • After compression 3.3 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. Myquiznos.com needs all CSS files to be minified and compressed as it can save up to 17.5 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

18

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

myquiznos.com

myquiznos.com

331 ms

myquiznos.com

myquiznos.com

252 ms

Login.aspx

Login.aspx

136 ms

main.css

main.css

91 ms

Window.css

Window.css

151 ms

WebResource.axd

WebResource.axd

282 ms

ScriptResource.axd

ScriptResource.axd

192 ms

ScriptResource.axd

ScriptResource.axd

327 ms

ScriptResource.axd

ScriptResource.axd

237 ms

WebResource.axd

WebResource.axd

191 ms

WebResource.axd

WebResource.axd

287 ms

quiznosLogo.gif

quiznosLogo.gif

238 ms

bannerBackground.jpg

bannerBackground.jpg

103 ms

login-button.jpg

login-button.jpg

136 ms

roundedLowerRight.gif

roundedLowerRight.gif

141 ms

roundedLowerLeft.gif

roundedLowerLeft.gif

156 ms

linkBarShadow.jpg

linkBarShadow.jpg

58 ms

footerLine.gif

footerLine.gif

52 ms

transp.gif

transp.gif

47 ms

ga.js

ga.js

25 ms

__utm.gif

__utm.gif

13 ms

SEO Factors

myquiznos.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myquiznos.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Myquiznos.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.

Social Sharing Optimization

myquiznos.com

Open Graph description is not detected on the main page of Myquiznos. 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: