12.4 sec in total
2.3 sec
9.4 sec
691 ms
Welcome to lime.tt homepage info - get ready to check Lime best content for Trinidad and Tobago right away, or after learning these important things about lime.tt
Lime.tt, the last place you check before you grab that wallet and keys. Event coverage, streaming, and reviews of bars, lounges, restaurants in Trinbago!
Visit lime.ttWe analyzed Lime.tt page load time and found that the first response time was 2.3 sec and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lime.tt performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value28.5 s
0/100
25%
Value19.8 s
0/100
10%
Value1,060 ms
25/100
30%
Value0.058
98/100
15%
Value27.8 s
0/100
10%
2265 ms
197 ms
216 ms
227 ms
208 ms
Our browser made a total of 171 requests to load all elements on the main page. We found that 49% of them (84 requests) were addressed to the original Lime.tt, 13% (23 requests) were made to Static.xx.fbcdn.net and 9% (15 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Lime.tt.
Page size can be reduced by 1.8 MB (49%)
3.6 MB
1.8 MB
In fact, the total size of Lime.tt main page is 3.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. 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 137.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 137.2 kB or 80% of the original size.
Potential reduce by 779.7 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, Lime needs image optimization as it can save up to 779.7 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 706.9 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 706.9 kB or 68% of the original size.
Potential reduce by 132.3 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. Lime.tt needs all CSS files to be minified and compressed as it can save up to 132.3 kB or 82% of the original size.
Number of requests can be reduced by 98 (58%)
169
71
The browser has sent 169 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lime. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
www.lime.tt
2265 ms
style.css
197 ms
style.css
216 ms
nextgen_gallery_related_images.css
227 ms
output.css
208 ms
events_manager.css
271 ms
sb-instagram.css
199 ms
flipbook.style.css
398 ms
font-awesome.css
465 ms
jquery.qtip.min.css
400 ms
gce-style.css
402 ms
jquery.fancybox-1.3.4.css
427 ms
photonic.css
425 ms
jquery.js
619 ms
jquery-migrate.min.js
474 ms
include.js
496 ms
ajax.js
517 ms
persist.js
580 ms
store.js
593 ms
ngg_store.js
595 ms
jquery.ui.core.min.js
641 ms
jquery.ui.widget.min.js
639 ms
jquery.ui.position.min.js
648 ms
jquery.ui.mouse.min.js
705 ms
jquery.ui.sortable.min.js
803 ms
jquery.ui.datepicker.min.js
744 ms
jquery.ui.menu.min.js
744 ms
jquery.ui.autocomplete.min.js
749 ms
jquery.ui.resizable.min.js
756 ms
jquery.ui.draggable.min.js
774 ms
jquery.ui.button.min.js
829 ms
jquery.ui.dialog.min.js
836 ms
events-manager.js
930 ms
jquery.t-countdown.js
856 ms
lightbox_context.js
903 ms
flipbook.min.js
1041 ms
spcjs.php
351 ms
addthis_widget.js
10 ms
style.css
861 ms
shailan-dropdown.min.css
747 ms
flexslider.css
844 ms
public.css
830 ms
public.css
777 ms
style.css
795 ms
embed.js
774 ms
photonic.js
716 ms
jquery.cycle.all.min.js
733 ms
jquery.fancybox-1.3.4.pack.js
748 ms
hoverIntent.min.js
753 ms
sb-instagram.js
765 ms
jquery.flexslider-min.js
717 ms
ga.js
9 ms
fbds.js
4 ms
spc.php
157 ms
fl.js
170 ms
25 ms
__utm.gif
20 ms
collect
60 ms
web-hosting-green-01.gif
305 ms
DIRECTV_NOT-LOSING-NUTTIN.jpg
739 ms
web-hosting-green-02.gif
300 ms
0.gif
298 ms
click1.jpg
341 ms
spacer.gif
300 ms
pop.jpg
339 ms
web-hosting-green-08.gif
340 ms
web-hosting-green-09.gif
338 ms
jaz.jpg
339 ms
cou.jpg
361 ms
cts.jpg
393 ms
flow.jpg
396 ms
hein.jpg
457 ms
honda.jpg
395 ms
fore.jpg
455 ms
sx.jpg
455 ms
mu.jpg
457 ms
00a-Cover.jpg
944 ms
iPhone-app.png
455 ms
web-hosting-green-12.gif
495 ms
web-hosting-green-13.gif
561 ms
web-hosting-green-07.gif
542 ms
web-hosting-green-10.gif
541 ms
light_bg_dash.png
541 ms
widgets.js
5 ms
social-twitter.gif
507 ms
social-facebook.gif
563 ms
social-linkedin.gif
571 ms
social-youtube.gif
574 ms
photos.footer.jpg
538 ms
web-hosting-green-11.gif
579 ms
recent
350 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
128 ms
300lo.json
87 ms
all.js&version=v2.0
113 ms
pinit00.png
59 ms
counter.5524cceca805eb4b9b2b.js
47 ms
sh.8e5f85691f9aaa082472a194.html
61 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
60 ms
likebox.php
416 ms
shares.json
46 ms
shares.json
39 ms
shares.json
42 ms
shares.json
103 ms
shares.json
42 ms
shares.json
40 ms
shares.json
41 ms
shares.json
42 ms
shares.json
40 ms
shares.json
40 ms
bg_direction_nav.png
376 ms
syndication
154 ms
354348660915576832
177 ms
194 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
53 ms
xd_arbiter.php
69 ms
xd_arbiter.php
77 ms
proxy.jpg
31 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
8 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
17 ms
1XhSFE5B_normal.jpeg
312 ms
Mv4fgDci_normal.jpg
320 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
55 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
93 ms
JILs2BHKnAI.css
89 ms
hnyz4lqaMhM.css
89 ms
vuvO6itHu-7.css
96 ms
q68gy-v_YMF.js
101 ms
FJmpeSpHpjS.js
100 ms
0wM5s1Khldu.js
95 ms
1bNoFZUdlYZ.js
94 ms
OloiM1PZafe.js
96 ms
LTv6ZK-5zxz.js
130 ms
1FCa-btixu2.js
127 ms
Oagsvfb4VWi.js
127 ms
pObvZSrFc_4.js
128 ms
Kt4tkgSRvHH.js
127 ms
H3EKDTObx05.js
157 ms
eR-qA8bp1RM.js
158 ms
nu-qg3EqU-e.js
159 ms
jot.html
4 ms
12799109_1307575892626996_1813345123089986290_n.jpg
124 ms
548610_364880433563218_106787061_n.jpg
25 ms
12376433_10156449214900226_7565786096654470877_n.jpg
136 ms
12801141_10156635284305338_1836679927313160863_n.jpg
25 ms
12088241_10154409659062923_9014108083660873796_n.jpg
27 ms
10527869_586512314837904_6346549738505874083_n.jpg
91 ms
10553390_191545087900136_8242052176889460224_n.jpg
24 ms
1604862_10153274142131720_6000830330154734097_n.jpg
24 ms
11169465_10155645094340285_3501076260724939253_n.jpg
25 ms
wL6VQj7Ab77.png
22 ms
s7jcwEQH7Sx.png
21 ms
gxbPuQdXIZP.png
21 ms
link_v1_e64f66f5650df987d97cc5f00c4cb5987f367028.svg
7 ms
jot.html
3 ms
I6-MnjEovm5.js
60 ms
pQrUxxo5oQp.js
59 ms
ping
124 ms
22 ms
jot
25 ms
like.php
185 ms
like.php
160 ms
like.php
217 ms
like.php
199 ms
like.php
224 ms
like.php
230 ms
like.php
226 ms
like.php
199 ms
like.php
188 ms
like.php
211 ms
qeKvIRsJabD.js
52 ms
LVx-xkvaJ0b.png
57 ms
lime.tt accessibility score
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
button, link, and menuitem elements do not have accessible names.
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
lime.tt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lime.tt SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lime.tt can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Lime.tt 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.
lime.tt
Open Graph data is detected on the main page of Lime. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: