10 sec in total
833 ms
8.8 sec
321 ms
Welcome to transple.com homepage info - get ready to check Transple best content for Taiwan right away, or after learning these important things about transple.com
阡陌之間,唯有Tranple,是你的最佳嚮導!身處交通之中,我們的服務將無所不在。
Visit transple.comWe analyzed Transple.com page load time and found that the first response time was 833 ms and then it took 9.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.
transple.com performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value3.1 s
74/100
25%
Value5.9 s
48/100
10%
Value260 ms
83/100
30%
Value0.065
97/100
15%
Value5.8 s
66/100
10%
833 ms
1444 ms
353 ms
889 ms
1057 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 94% of them (60 requests) were addressed to the original Transple.com, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.4 sec) belongs to the original domain Transple.com.
Page size can be reduced by 1.9 MB (48%)
3.9 MB
2.0 MB
In fact, the total size of Transple.com main page is 3.9 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.8 MB which makes up the majority of the site volume.
Potential reduce by 460.6 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 460.6 kB or 88% of the original size.
Potential reduce by 198.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. Obviously, Transple needs image optimization as it can save up to 198.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 540.0 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 540.0 kB or 69% of the original size.
Potential reduce by 676.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. Transple.com needs all CSS files to be minified and compressed as it can save up to 676.0 kB or 87% of the original size.
Number of requests can be reduced by 33 (54%)
61
28
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Transple. 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 from 15 to 1 for CSS and as a result speed up the page load time.
transple.com
833 ms
styles.css
1444 ms
style-red.css
353 ms
less.js
889 ms
bootstrap.css
1057 ms
css
24 ms
css
37 ms
font-awesome.css
557 ms
slicknav.css
527 ms
owl.carousel.css
558 ms
navstylechange.css
703 ms
settings.css
1104 ms
animate.css
937 ms
prettyPhoto.css
1054 ms
jquery-ui-datepicker.min.css
1063 ms
thsr-groupbuy.css
1126 ms
customized.css
1227 ms
modernizr.js
862 ms
jquery-1.11.1.min.js
1052 ms
owl.carousel.min.js
920 ms
bootstrap.min.js
947 ms
jquery.slicknav.min.js
1036 ms
jquery-scrolltofixed-min.js
1037 ms
jquery-1.7.2.min.js
6427 ms
jquery-ui-datepicker.min.js
6428 ms
wow.js
6423 ms
layout.js
6424 ms
jquery.parallax-1.1.3.js
6424 ms
jquery.prettyPhoto.js
6425 ms
script.js
6426 ms
ptt_ajax_v1.js
6428 ms
transple.js
6429 ms
thsr_schedule.js
6426 ms
jquery.themepunch.tools.min.js
6428 ms
jquery.themepunch.revolution.min.js
6428 ms
logo.png
265 ms
dummy.png
262 ms
1_1.jpg
536 ms
1_3.jpg
503 ms
1_2.jpg
562 ms
1_4.jpg
530 ms
1_5.jpg
714 ms
1_6.jpg
573 ms
1_7.jpg
641 ms
1_8.jpg
885 ms
1_9.jpg
715 ms
1_10.jpg
750 ms
1_11.jpg
764 ms
1_12.jpg
807 ms
79card.png
1412 ms
port-sm-111.jpg
893 ms
port-sm-222.jpg
920 ms
port-sm-333.jpg
941 ms
port-sm-444.jpg
971 ms
port-sm-555.jpg
1056 ms
port-sm-666.jpg
1083 ms
port-sm-777.jpg
1114 ms
1217 ms
fontawesome-webfont.woff
858 ms
analytics.js
140 ms
loader.gif
737 ms
collect
33 ms
entrybg5.jpg
912 ms
pad4.png
1032 ms
transple.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
Links do not have a discernible name
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.
transple.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
transple.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
JA
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Transple.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Transple.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.
transple.com
Open Graph data is detected on the main page of Transple. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: