Tools & Wizards About Us
711.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

711.com

Page Load Speed

2.4 sec in total

First Response

16 ms

Resources Loaded

1.7 sec

Page Rendered

668 ms

711.com screenshot

About Website

Visit 711.com now to see the best up-to-date 711 content and also check out these interesting facts you probably never knew about 711.com

7-Eleven is your go-to convenience store for food, snacks, hot and cold beverages, gas and so much more. Generally open 24 hours a day.

Visit 711.com

Key Findings

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

Performance Metrics

711.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value5,900 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.651

9/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

711.com

16 ms

www.7-eleven.com

57 ms

cted-the-Swinde-veriend-World-inniest-saw-his-Ho

37 ms

donotsell-extended.min.css

95 ms

donotsell-block.min.js

104 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 711.com, 62% (44 requests) were made to 7-eleven.com and 15% (11 requests) were made to Kit-uploads.fontawesome.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source 7-eleven.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 249.5 kB (24%)

Content Size

1.1 MB

After Optimization

807.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 711.com main page is 1.1 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. 70% of websites need less resources to load. Images take 557.5 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 249.2 kB

  • Original 299.9 kB
  • After minification 299.9 kB
  • After compression 50.7 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 249.2 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 557.5 kB
  • After minification 557.5 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. 711 images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 258 B

  • Original 199.3 kB
  • After minification 199.3 kB
  • After compression 199.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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 10 B

  • Original 211 B
  • After minification 211 B
  • After compression 201 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. 711.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

51

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

711.com

711.com

16 ms

www.7-eleven.com

www.7-eleven.com

57 ms

cted-the-Swinde-veriend-World-inniest-saw-his-Ho

cted-the-Swinde-veriend-World-inniest-saw-his-Ho

37 ms

donotsell-extended.min.css

donotsell-extended.min.css

95 ms

donotsell-block.min.js

donotsell-block.min.js

104 ms

js

js

191 ms

newrelic-browser-prod.js

newrelic-browser-prod.js

28 ms

main.min.js

main.min.js

345 ms

ee81968da0.js

ee81968da0.js

190 ms

embed.js

embed.js

95 ms

a188449440a7709f.css

a188449440a7709f.css

31 ms

e4c41ab970682c4f.css

e4c41ab970682c4f.css

32 ms

b36d6fbb3e8fd053.css

b36d6fbb3e8fd053.css

27 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

33 ms

webpack-dbd4b8b2f1e5de6b.js

webpack-dbd4b8b2f1e5de6b.js

175 ms

framework-16e7f16798adb2a9.js

framework-16e7f16798adb2a9.js

94 ms

main-fd772e756f96d815.js

main-fd772e756f96d815.js

95 ms

_app-b4c2f7fc1fb3d094.js

_app-b4c2f7fc1fb3d094.js

194 ms

7692-dc45c98a1f219a02.js

7692-dc45c98a1f219a02.js

94 ms

8803-c868a77930a840dd.js

8803-c868a77930a840dd.js

183 ms

3811-85fdb96eaa2c8da5.js

3811-85fdb96eaa2c8da5.js

102 ms

7806-34ceb5db86c55b8f.js

7806-34ceb5db86c55b8f.js

183 ms

5116-dcbd0f25429b0b15.js

5116-dcbd0f25429b0b15.js

174 ms

6166-8b4ee34169c2975f.js

6166-8b4ee34169c2975f.js

185 ms

4397-5d0f5d50e2f36dfe.js

4397-5d0f5d50e2f36dfe.js

186 ms

8084-a8e71c34570a22d1.js

8084-a8e71c34570a22d1.js

187 ms

6402-17ad6546bece0fc0.js

6402-17ad6546bece0fc0.js

187 ms

290-91cac61a7a0c61b2.js

290-91cac61a7a0c61b2.js

189 ms

6046-7db3be309cd17a69.js

6046-7db3be309cd17a69.js

190 ms

index-4318848ec308607b.js

index-4318848ec308607b.js

189 ms

_buildManifest.js

_buildManifest.js

190 ms

_ssgManifest.js

_ssgManifest.js

190 ms

_Incapsula_Resource

_Incapsula_Resource

187 ms

7e-logo-color.svg

7e-logo-color.svg

45 ms

image

image

46 ms

image

image

196 ms

image

image

172 ms

image

image

46 ms

image

image

47 ms

image

image

169 ms

image

image

169 ms

image

image

170 ms

image

image

218 ms

image

image

217 ms

image

image

218 ms

image

image

216 ms

7e-logo-white.svg

7e-logo-white.svg

218 ms

RightGrotesk-CompactDark.woff

RightGrotesk-CompactDark.woff

1123 ms

pro.min.js

pro.min.js

1083 ms

_Incapsula_Resource

_Incapsula_Resource

1026 ms

KFOlCnqEu92Fr1MmYUtfBBc-.woff

KFOlCnqEu92Fr1MmYUtfBBc-.woff

1069 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

1091 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

1125 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

1105 ms

RightGrotesk-Bold.woff

RightGrotesk-Bold.woff

993 ms

37126D_1_0.woff

37126D_1_0.woff

1205 ms

ns

ns

1070 ms

collector

collector

1157 ms

burger-3.svg

burger-3.svg

117 ms

sandwich-2.svg

sandwich-2.svg

125 ms

snack-1.svg

snack-1.svg

175 ms

coffee-1.svg

coffee-1.svg

174 ms

juice-1.svg

juice-1.svg

173 ms

shirt-icon-1.svg

shirt-icon-1.svg

170 ms

logo-twitter-1.svg

logo-twitter-1.svg

167 ms

facebook-solid-1.svg

facebook-solid-1.svg

140 ms

instagram-solid-1.svg

instagram-solid-1.svg

167 ms

x-twitter-solid-1.svg

x-twitter-solid-1.svg

172 ms

youtube-solid-1.svg

youtube-solid-1.svg

201 ms

bars.svg

bars.svg

93 ms

generic1726992848463.js

generic1726992848463.js

30 ms

Accessibility Review

711.com accessibility score

98

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

Links do not have a discernible name

Best Practices

711.com best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

711.com SEO score

77

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

Links do not have descriptive text

High

Document doesn't have a valid hreflang

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 711.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that 711.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

711.com

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