Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

1112.com

เดอะ พิซซ่า คอมปะนี 1112 ออนไลน์ดิลิเวอรี ซื้อกลับ

Page Load Speed

7.3 sec in total

First Response

1.2 sec

Resources Loaded

5.4 sec

Page Rendered

683 ms

1112.com screenshot

About Website

Click here to check amazing 1112 content for Thailand. Otherwise, check out these important facts you probably never knew about 1112.com

สั่งออนไลน์ได้แล้ววันนี้ที่ www.1112.com หรือ แอพพลิเคชั่น เดอะ พิซซ่า คอมปะนี หรือ โทร 1112

Visit 1112.com

Key Findings

We analyzed 1112.com page load time and found that the first response time was 1.2 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

1112.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value25.1 s

0/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value2,000 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.245

51/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

1112.com

1213 ms

reset.css

566 ms

flexslider.css

568 ms

style.css

850 ms

jquery-ui.min.css

570 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 74% of them (43 requests) were addressed to the original 1112.com, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Bcp.crwdcntrl.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain 1112.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 588.2 kB (23%)

Content Size

2.5 MB

After Optimization

1.9 MB

In fact, the total size of 1112.com main page is 2.5 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. 50% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 33.9 kB

  • Original 41.1 kB
  • After minification 34.7 kB
  • After compression 7.2 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 6.4 kB, which is 16% 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 33.9 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 89.2 kB

  • Original 1.8 MB
  • After minification 1.7 MB

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. 1112 images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 343.2 kB

  • Original 527.8 kB
  • After minification 506.9 kB
  • After compression 184.6 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 343.2 kB or 65% of the original size.

CSS Optimization

-82%

Potential reduce by 121.8 kB

  • Original 148.0 kB
  • After minification 114.0 kB
  • After compression 26.1 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. 1112.com needs all CSS files to be minified and compressed as it can save up to 121.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (37%)

Requests Now

52

After Optimization

33

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1112. 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 from 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

1112.com 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 input fields do not have accessible names

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

1112.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

1112.com 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

    TH

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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