7.6 sec in total
1.5 sec
5.8 sec
260 ms
Visit witty.co.th now to see the best up-to-date Witty content for Thailand and also check out these interesting facts you probably never knew about witty.co.th
????˹ѧ??????ͤ??ѡ??? ͺ?? Joomla! ͺ?? osCommerce ͺ?? Moodle ͺ?? Drupal ͺ?? CMS
Visit witty.co.thWe analyzed Witty.co.th page load time and found that the first response time was 1.5 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
witty.co.th performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value5.8 s
15/100
25%
Value7.0 s
32/100
10%
Value730 ms
40/100
30%
Value0
100/100
15%
Value8.5 s
38/100
10%
1540 ms
260 ms
540 ms
9 ms
774 ms
Our browser made a total of 28 requests to load all elements on the main page. We found that 50% of them (14 requests) were addressed to the original Witty.co.th, 18% (5 requests) were made to Lvs.truehits.in.th and 14% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Witty.co.th.
Page size can be reduced by 96.5 kB (10%)
926.0 kB
829.5 kB
In fact, the total size of Witty.co.th main page is 926.0 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. 20% of websites need less resources to load. Images take 877.0 kB which makes up the majority of the site volume.
Potential reduce by 16.1 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. This page needs HTML code to be minified as it can gain 6.7 kB, which is 34% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 16.1 kB or 81% of the original size.
Potential reduce by 59.8 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. Witty images are well optimized though.
Potential reduce by 14.3 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 14.3 kB or 68% of the original size.
Potential reduce by 6.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. Witty.co.th needs all CSS files to be minified and compressed as it can save up to 6.3 kB or 79% of the original size.
Number of requests can be reduced by 9 (33%)
27
18
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Witty. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
index.php
1540 ms
BrightSide.css
260 ms
t0031585.js
540 ms
show_ads.js
9 ms
logo.jpg
774 ms
bg.gif
261 ms
headerbg.gif
523 ms
coverpic_196_ebstore02.png
1297 ms
coverpic_197_infog.png
1301 ms
coverpic_140_ssgalaxy03.png
1558 ms
coverpic_181_aliba.png
1312 ms
coverpic_190_adwords02.png
1558 ms
coverpic_173_fixtab.png
1821 ms
coverpic_174_sworks03.png
2331 ms
th_donate_1.8.js
865 ms
th_common_1.4.js
871 ms
ckid2.php
893 ms
showfixads.php
841 ms
goggen.php
575 ms
tableft.gif
406 ms
showfix.php
554 ms
ckid3.php
534 ms
fixadlib.js
546 ms
tabright.gif
260 ms
ca-pub-9122858791028333.js
60 ms
zrt_lookup.html
56 ms
show_ads_impl.js
98 ms
osd.js
13 ms
witty.co.th 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
[aria-*] attributes do not match their roles
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
witty.co.th 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
General
Impact
Issue
Browser errors were logged to the console
witty.co.th SEO score
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
EN
EN
TIS-620
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Witty.co.th 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 Witty.co.th main page’s claimed encoding is tis-620. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
witty.co.th
Open Graph description is not detected on the main page of Witty. 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: