Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

Page Load Speed

1.5 sec in total

First Response

522 ms

Resources Loaded

855 ms

Page Rendered

107 ms

giantpizzaking.net screenshot

About Website

Click here to check amazing Giantpizzaking content. Otherwise, check out these important facts you probably never knew about giantpizzaking.net

Visit giantpizzaking.net

Key Findings

We analyzed Giantpizzaking.net page load time and found that the first response time was 522 ms and then it took 962 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

giantpizzaking.net performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value1.7 s

100/100

10%

Network Requests Diagram

giantpizzaking.net

522 ms

pizza.css

155 ms

nadanada_01.jpg

232 ms

spacer.gif

79 ms

index_12.jpg

162 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that all of those requests were addressed to Giantpizzaking.net and no external sources were called. The less responsive or slowest element that took the longest time to load (522 ms) belongs to the original domain Giantpizzaking.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 24.2 kB (30%)

Content Size

81.3 kB

After Optimization

57.1 kB

In fact, the total size of Giantpizzaking.net main page is 81.3 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 64.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 13.3 kB

  • Original 16.4 kB
  • After minification 12.9 kB
  • After compression 3.1 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 3.6 kB, which is 22% 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 13.3 kB or 81% of the original size.

Image Optimization

-16%

Potential reduce by 10.5 kB

  • Original 64.3 kB
  • After minification 53.8 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. Obviously, Giantpizzaking needs image optimization as it can save up to 10.5 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-69%

Potential reduce by 358 B

  • Original 522 B
  • After minification 422 B
  • After compression 164 B

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. Giantpizzaking.net needs all CSS files to be minified and compressed as it can save up to 358 B or 69% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Giantpizzaking. According to our analytics all requests are already optimized.

Accessibility Review

giantpizzaking.net accessibility score

94

Accessibility Issues

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

Document doesn't have a <title> element

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

giantpizzaking.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

giantpizzaking.net SEO score

83

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Document doesn't have a <title> element

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

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Giantpizzaking.net 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 Giantpizzaking.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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