7.4 sec in total
900 ms
6.2 sec
242 ms
Visit mobile.teenee.com now to see the best up-to-date Mobile Teenee content for Thailand and also check out these interesting facts you probably never knew about mobile.teenee.com
Visit mobile.teenee.comWe analyzed Mobile.teenee.com page load time and found that the first response time was 900 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mobile.teenee.com performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value9.7 s
0/100
25%
Value10.3 s
8/100
10%
Value3,250 ms
2/100
30%
Value0.301
39/100
15%
Value11.8 s
17/100
10%
900 ms
584 ms
551 ms
554 ms
835 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 79% of them (63 requests) were addressed to the original Mobile.teenee.com, 6% (5 requests) were made to Pagead2.googlesyndication.com and 5% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Lvs.truehits.in.th.
Page size can be reduced by 353.2 kB (30%)
1.2 MB
826.0 kB
In fact, the total size of Mobile.teenee.com main page is 1.2 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. 55% of websites need less resources to load. Images take 751.8 kB which makes up the majority of the site volume.
Potential reduce by 86.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 86.2 kB or 88% of the original size.
Potential reduce by 30.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. Mobile Teenee images are well optimized though.
Potential reduce by 123.4 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 123.4 kB or 65% of the original size.
Potential reduce by 113.0 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. Mobile.teenee.com needs all CSS files to be minified and compressed as it can save up to 113.0 kB or 82% of the original size.
Number of requests can be reduced by 19 (24%)
79
60
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile Teenee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
mobile.teenee.com
900 ms
bootstrap.css
584 ms
font-awesome.css
551 ms
style.css
554 ms
jquery.js
835 ms
jquery-migrate.min.js
556 ms
responsive-modernizr.js
573 ms
bootstrap.js
821 ms
strap-extras.js
822 ms
jquery.imagesloaded.js
829 ms
jquery.wookmark.js
875 ms
a0000583.js
662 ms
responsive-scripts.js
876 ms
responsive-plugins.js
1087 ms
jquery.colorbox-min.js
1092 ms
292 ms
slogan.png
288 ms
Nx70xlogo.png.pagespeed.ic.vpZ5w_IMtp.jpg
278 ms
url.png
276 ms
ajax-loader.gif
481 ms
bangna-new-webfont.woff
744 ms
th_donate_1.8.js
914 ms
th_common_1.4.js
914 ms
goggen.php
2959 ms
data.php
671 ms
_ads_13_pin_topic.php
294 ms
300xNx74.jpg,q90295487.pagespeed.ic.-uXavYj15-.jpg
302 ms
73.jpg
286 ms
72.jpg
551 ms
71.jpg
283 ms
69.jpg
543 ms
68.jpg
548 ms
67.jpg
828 ms
66.jpg
575 ms
65.jpg
588 ms
64.jpg
1077 ms
62.jpg
818 ms
61.jpg
823 ms
60.jpg
1446 ms
59.jpg
862 ms
58.jpg
1089 ms
57.jpg
1096 ms
56.jpg
1100 ms
55.jpg
1148 ms
54.jpg
1346 ms
53.jpg
1360 ms
52.jpg
1369 ms
51.jpg
1373 ms
50.jpg
2024 ms
49.jpg
1614 ms
48.jpg
1631 ms
47.jpg
1643 ms
46.jpg
1920 ms
45.jpg
1733 ms
41.jpg
1884 ms
40.jpg
1901 ms
39.jpg
1917 ms
38.jpg
2025 ms
37.jpg
2154 ms
35.jpg
2172 ms
34.jpg
2198 ms
fontawesome-webfont.woff
2466 ms
33.jpg
2025 ms
adsbygoogle.js
15 ms
32.jpg
2032 ms
30.jpg
2130 ms
ca-pub-1385876742352503.js
47 ms
zrt_lookup.html
57 ms
show_ads_impl.js
65 ms
ads
1556 ms
osd.js
10 ms
data.php
2258 ms
29.jpg
2047 ms
11143756423607285033
48 ms
abg.js
51 ms
m_js_controller.js
66 ms
googlelogo_color_112x36dp.png
35 ms
x_button_blue2.png
6 ms
s
21 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
4 ms
mobile.teenee.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
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
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.
mobile.teenee.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
mobile.teenee.com SEO score
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
TH
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.teenee.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 Mobile.teenee.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.
mobile.teenee.com
Open Graph description is not detected on the main page of Mobile Teenee. 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: