Tools & Wizards About Us
tockereyes.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

tockereyes.com

快三APP-有限公司

Page Load Speed

7.3 sec in total

First Response

128 ms

Resources Loaded

4.8 sec

Page Rendered

2.3 sec

tockereyes.com screenshot

About Website

Welcome to tockereyes.com homepage info - get ready to check Tockereyes best content right away, or after learning these important things about tockereyes.com

快三APP-有限公司

Visit tockereyes.com

Key Findings

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

Performance Metrics

tockereyes.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.5 s

0/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value1,060 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.326

35/100

15%

TTI (Time to Interactive)

Value18.3 s

3/100

10%

Network Requests Diagram

tockereyes.com

128 ms

4605-kirkwood-hwy

204 ms

gtm.js

184 ms

xng6zjv.css

180 ms

main.9b278a99.css

46 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tockereyes.com, 30% (21 requests) were made to Locations.myeyedr.com and 17% (12 requests) were made to Dynl.mktgcdn.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Dynl.mktgcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 117.2 kB (21%)

Content Size

554.9 kB

After Optimization

437.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tockereyes.com main page is 554.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 302.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 98.6 kB

  • Original 122.9 kB
  • After minification 122.7 kB
  • After compression 24.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. 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 98.6 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 17.4 kB

  • Original 302.9 kB
  • After minification 285.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. Tockereyes images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.3 kB

  • Original 129.1 kB
  • After minification 129.1 kB
  • After compression 127.8 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

-0%

Potential reduce by 0 B

  • Original 5 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.

Requests Breakdown

Number of requests can be reduced by 34 (59%)

Requests Now

58

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tockereyes.com

tockereyes.com

128 ms

4605-kirkwood-hwy

4605-kirkwood-hwy

204 ms

gtm.js

gtm.js

184 ms

xng6zjv.css

xng6zjv.css

180 ms

main.9b278a99.css

main.9b278a99.css

46 ms

main.1f87d3b7.js

main.1f87d3b7.js

126 ms

BypassPagespeed.51317649.js

BypassPagespeed.51317649.js

125 ms

optimize.js

optimize.js

148 ms

p.css

p.css

246 ms

optimize.js

optimize.js

1496 ms

bat.js

bat.js

1553 ms

js

js

732 ms

analytics.js

analytics.js

1459 ms

225x225.png

225x225.png

1889 ms

Menu.96b06d2f.svg

Menu.96b06d2f.svg

1329 ms

MenuX.35cbd0ce.svg

MenuX.35cbd0ce.svg

1317 ms

angle.c0b9bb24.svg

angle.c0b9bb24.svg

1255 ms

phone.1658a349.png

phone.1658a349.png

1335 ms

directions.178f7595.svg

directions.178f7595.svg

1328 ms

uber.a0a8383e.svg

uber.a0a8383e.svg

1424 ms

pin.83d7c55b.svg

pin.83d7c55b.svg

1451 ms

600x337.jpg

600x337.jpg

1850 ms

600x337.jpg

600x337.jpg

1849 ms

600x337.jpg

600x337.jpg

1849 ms

600x300.png

600x300.png

2016 ms

600x300.png

600x300.png

2058 ms

600x300.png

600x300.png

2067 ms

600x300.png

600x300.png

2068 ms

96x96.png

96x96.png

2069 ms

96x96.png

96x96.png

2068 ms

96x96.png

96x96.png

2072 ms

fbevents.js

fbevents.js

1454 ms

up_loader.1.1.0.js

up_loader.1.1.0.js

1503 ms

di.js

di.js

1507 ms

d

d

842 ms

d

d

1133 ms

d

d

1276 ms

GothamHTF-Book.f3336521.woff

GothamHTF-Book.f3336521.woff

876 ms

GothamHTF-Light.6cf3be29.woff

GothamHTF-Light.6cf3be29.woff

877 ms

GothamHTF-Bold.3accf4d2.woff

GothamHTF-Bold.3accf4d2.woff

1035 ms

1900x1068.jpg

1900x1068.jpg

2419 ms

angle-right.fe79b532.svg

angle-right.fe79b532.svg

485 ms

angle-right-gray.c5d3b0e9.svg

angle-right-gray.c5d3b0e9.svg

580 ms

store_pagespixel

store_pagespixel

862 ms

0.f167028a.js

0.f167028a.js

900 ms

0.4b6154e8.js

0.4b6154e8.js

686 ms

js

js

875 ms

dropdown-angle.b7c0f8d5.svg

dropdown-angle.b7c0f8d5.svg

639 ms

lines.813363c3.png

lines.813363c3.png

849 ms

4605-kirkwood-hwy

4605-kirkwood-hwy

808 ms

roundtrip.js

roundtrip.js

1773 ms

d

d

630 ms

d

d

631 ms

linkid.js

linkid.js

663 ms

collect

collect

1597 ms

collect

collect

593 ms

collect

collect

1015 ms

2022271908061931

2022271908061931

822 ms

gen_204

gen_204

690 ms

common.js

common.js

61 ms

util.js

util.js

28 ms

controls.js

controls.js

404 ms

collect

collect

521 ms

index.js

index.js

130 ms

infowindow.js

infowindow.js

115 ms

T4I5MHFJVRGHZAHQCNRZCM

T4I5MHFJVRGHZAHQCNRZCM

160 ms

223 ms

ga-audiences

ga-audiences

168 ms

UWPRO4RXIVFCPL4HXLHMY7.js

UWPRO4RXIVFCPL4HXLHMY7.js

19 ms

Accessibility Review

tockereyes.com accessibility score

81

Accessibility Issues

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.

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

tockereyes.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

tockereyes.com SEO score

83

Search Engine Optimization Advices

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

    ZH

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

tockereyes.com

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