3.6 sec in total
1.4 sec
2 sec
210 ms
Welcome to checkyearly.com homepage info - get ready to check Checkyearly best content right away, or after learning these important things about checkyearly.com
Visit checkyearly.comWe analyzed Checkyearly.com page load time and found that the first response time was 1.4 sec and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
checkyearly.com performance score
name
value
score
weighting
Value1.5 s
96/100
10%
Value2.4 s
91/100
25%
Value2.1 s
99/100
10%
Value540 ms
55/100
30%
Value0.009
100/100
15%
Value3.4 s
92/100
10%
1371 ms
16 ms
22 ms
23 ms
17 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 79% of them (57 requests) were addressed to the original Checkyearly.com, 14% (10 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Checkyearly.com.
Page size can be reduced by 372.1 kB (24%)
1.6 MB
1.2 MB
In fact, the total size of Checkyearly.com main page is 1.6 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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 34.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. 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 34.2 kB or 79% of the original size.
Potential reduce by 76.3 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. Checkyearly images are well optimized though.
Potential reduce by 159.2 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 159.2 kB or 60% of the original size.
Potential reduce by 102.4 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. Checkyearly.com needs all CSS files to be minified and compressed as it can save up to 102.4 kB or 80% of the original size.
Number of requests can be reduced by 32 (52%)
61
29
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Checkyearly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
checkyearly.com
1371 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
16 ms
css_Q7R7Blo9EYqLDI5rIlO_T3uTFBjIXjLpcqMHjTvVdmg.css
22 ms
css_YzL_Vu33rKE8t-h7LPaPorN_53ja2y8sJfUi6JPwBao.css
23 ms
css_A7bIHwb6MfrYW8BX3fv3YSGe42Qosf_VmgSQQBI80HQ.css
17 ms
css
28 ms
css_NG-jQ-t5GDRA7WAzY2PzX-DpqZqK7FUvMiLkez_VhU4.css
19 ms
css_ulf66VM_c3O8KdJInVsAKBrR9LD_kV_lYpzM1-fVw_U.css
27 ms
css_0iNEbzWm7n65HwflK7KSqVL66ZRSuyJ0bF_hYUIdk5Q.css
23 ms
jquery.min.js
9 ms
jquery.once.js
23 ms
drupal.js
44 ms
jquery.fitvids.js
23 ms
jquery-ui.min.js
9 ms
fitvids.js
24 ms
jquery.colorbox-min.js
61 ms
colorbox.js
41 ms
colorbox_load.js
61 ms
colorbox_inline.js
62 ms
lightbox.js
62 ms
tvc_slideshow.js
69 ms
tvc.js
64 ms
jquery-ui-1.10.3.custom.min.js
65 ms
perfect-scrollbar-0.4.5.with-mousewheel.min.js
62 ms
jquery.sidr.js
63 ms
jquery.cycle-swipe.js
63 ms
jquery.cycle2.js
63 ms
jquery.cycle2.caption2.min.js
64 ms
tvc_colorbox.js
64 ms
jquery.qtip.min.js
64 ms
imagesloaded.pkg.min.js
65 ms
jquery.formalize.js
64 ms
omega-mediaqueries.js
64 ms
ga.js
7 ms
menu-collapsed.png
100 ms
menu-leaf.png
101 ms
the-vision-council.png
98 ms
social-facebook.png
100 ms
social-linkedin.png
99 ms
social-twitter.png
99 ms
social-youtube.png
100 ms
TVCorg%20consumer%20slideshow%20graphic.jpg
468 ms
eyecessorize_logo_grey-300px.png
328 ms
DES2016_WebSlider.png
420 ms
TVC-Slideshow-Image-UV_report.jpg
419 ms
TVC-Slideshow-Image---LowVis_report.jpg
387 ms
TVC-Slideshow-Image-LensCampaign_Mantle.jpg
463 ms
slideshow-lowvision_0.jpg
415 ms
img-adults_2.jpg
443 ms
img-teens_2.jpg
442 ms
img-children_2.jpg
448 ms
EyecessorizeSidebarGraphic.jpg
459 ms
2016_Digital_Eye_Strain_Report_cover.jpg
474 ms
logo_thinkaboutyoureyes_2.png
452 ms
logo_eyecessorize_2.png
461 ms
Visionexpo_2015.png
468 ms
logo_lowvision_2.png
472 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
97 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
97 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
98 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
97 ms
4cKlrioa77J2iqTqBgkRWg.ttf
98 ms
__utm.gif
21 ms
bg_tab.png
381 ms
css_ulf66VM_c3O8KdJInVsAKBrR9LD_kV_lYpzM1-fVw_U.css
379 ms
LqowQDslGv4DmUBAfWa2Vw.ttf
17 ms
2HG_tEPiQ4Z6795cGfdivKCWcynf_cDxXwCLxiixG1c.ttf
19 ms
gc5ZVKiLNkRdGlU3GaSVBfesZW2xOQ-xsNqO47m55DA.ttf
19 ms
HkF_qI1x_noxlxhrhMQYEKCWcynf_cDxXwCLxiixG1c.ttf
18 ms
VNUH7ZAcagYBWsAiBBCEY6CWcynf_cDxXwCLxiixG1c.ttf
18 ms
slideshow-left.png
20 ms
slideshow-right.png
16 ms
checkyearly.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
checkyearly.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
checkyearly.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Checkyearly.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 Checkyearly.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.
checkyearly.com
Open Graph description is not detected on the main page of Checkyearly. 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: