6.6 sec in total
533 ms
5.8 sec
239 ms
Welcome to uupon.tw homepage info - get ready to check Uupon best content for Taiwan right away, or after learning these important things about uupon.tw
以悠遊卡為會員識別的紅利點數平台,只要加入UUPON會員並綁定悠遊卡,就可以在合作特約商累兌點服務。
Visit uupon.twWe analyzed Uupon.tw page load time and found that the first response time was 533 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
uupon.tw performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value14.9 s
0/100
25%
Value15.1 s
1/100
10%
Value2,960 ms
3/100
30%
Value0.26
47/100
15%
Value25.2 s
0/100
10%
533 ms
979 ms
127 ms
133 ms
101 ms
Our browser made a total of 176 requests to load all elements on the main page. We found that 40% of them (71 requests) were addressed to the original Uupon.tw, 8% (14 requests) were made to Cdnjs.cloudflare.com and 8% (14 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Uupon.tw.
Page size can be reduced by 697.4 kB (8%)
8.4 MB
7.7 MB
In fact, the total size of Uupon.tw main page is 8.4 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. Only a small number of websites need less resources to load. Images take 7.1 MB which makes up the majority of the site volume.
Potential reduce by 91.3 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 14.9 kB, which is 13% 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 91.3 kB or 80% of the original size.
Potential reduce by 96.9 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. Uupon images are well optimized though.
Potential reduce by 277.1 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 277.1 kB or 31% of the original size.
Potential reduce by 232.1 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. Uupon.tw needs all CSS files to be minified and compressed as it can save up to 232.1 kB or 87% of the original size.
Number of requests can be reduced by 87 (54%)
162
75
The browser has sent 162 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uupon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
uupon.tw
533 ms
uupon.tw
979 ms
css
127 ms
icon
133 ms
font-awesome.min.css
101 ms
materialdesignicons_1_4_57.min.css
370 ms
tether.min.css
120 ms
bootstrap.min.css
104 ms
bootstrap-material-design.min.css
738 ms
ripples.min.css
571 ms
snackbar.min.css
118 ms
ie.css
572 ms
smartbanner.min.css
572 ms
sweetalert2.min.css
120 ms
animate.min.css
113 ms
owl.carousel.min.css
116 ms
global.css
1114 ms
jquery-2.1.1.min.js
94 ms
adsbygoogle.js
142 ms
js
147 ms
js
192 ms
jquery.cycle.all.js
931 ms
jquery.carouFredSel.packed.js
119 ms
jquery.transit.min.js
113 ms
jquery.touchSwipe.min.js
122 ms
jquery.ba-throttle-debounce.min.js
119 ms
tether.min.js
120 ms
bootstrap.min.js
115 ms
material.min.js
754 ms
ripples.min.js
752 ms
smartbanner.min.js
936 ms
es6-promise.auto.min.js
117 ms
sweetalert2.min.js
245 ms
owl.carousel.min.js
119 ms
hammer.min.js
121 ms
swipe.min.js
243 ms
common.js
915 ms
ie10-viewport-bug-workaround.js
109 ms
bundle.js
1314 ms
gtm.js
156 ms
fbevents.js
156 ms
openbook.png
210 ms
logo.svg
333 ms
icon_Search.png
333 ms
icon_FB.png
338 ms
logo_outlined.svg
335 ms
2018btn-01.png
331 ms
left.png
331 ms
close.png
548 ms
introduce_uupon1.png
798 ms
introduce_uupon1_mb.png
1195 ms
introduce_uupon2.png
547 ms
introduce_uupon2_mb.png
798 ms
introduce_uupon3.png
547 ms
introduce_uupon3_mb.png
827 ms
introduce_uupon4.png
822 ms
introduce_uupon4_mb.png
976 ms
introduce_uupon5.png
915 ms
introduce_uupon5_mb.png
1194 ms
right_arrow.png
1178 ms
right.png
1193 ms
detail.do
1217 ms
detail.do
1296 ms
detail.do
1442 ms
5c7338243600000092e6a97145aded0d.jpg
1606 ms
5c113c3f3200000035fc816e1e2885fd.jpg
2187 ms
5c8d29e276000000ce345e8b37283675.jpg
2060 ms
5c25d1d0fb000000f878032ea4f42af4.jpg
1948 ms
5c25d1756a0000006b37ee1933cb81eb.jpg
1897 ms
5aeb2610ec00000018cbf0a4915545d7.jpg
2198 ms
5ac7634558000000900f26d8f5f340b4.jpg
2058 ms
5ac2274fff000000bde8283826709e16.jpg
2272 ms
5c68b136fa000000b4a2c644505364c9.jpg
2273 ms
5c68b28304000000ed47bf80c89cd2c2.jpg
2391 ms
5a0893aeed0000004a3bcb5b192f69ee.jpg
2579 ms
59f36ae8750000009e812d2a35caf174.jpg
2372 ms
59aca7dd9a000000cb36e031ec16e08f.jpg
2379 ms
sdk.js
73 ms
57330f300800000075599153fa953ad2.jpg
2325 ms
sdk.js
13 ms
fontawesome-webfont.woff
38 ms
show_ads_impl.js
77 ms
5c68ad19350000005535.jpg
2132 ms
5c58441cdc000003b135.jpg
2231 ms
57330f8b120000020652.jpg
2235 ms
5973c16d58000005fe1f.jpg
2246 ms
5aeb24585000000000b2.jpg
2317 ms
59aca7179c0000043944.jpg
2311 ms
zrt_lookup.html
39 ms
ads
403 ms
ads
393 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
85 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
100 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
108 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
107 ms
ads
755 ms
page.php
118 ms
5c11303ac50000034e32.jpg
2203 ms
5aeb3bf6ce0000073000.jpg
2208 ms
3119538a84000006a3c7.jpg
2222 ms
otoKjNgXJiB.css
33 ms
DyHqqElLeTe.js
44 ms
E_P-TzY6wm3.js
40 ms
kUkWpdn-FbF.js
74 ms
IdaDUxNeWGd.js
77 ms
fFBZSPO6Swz.js
76 ms
p55HfXW__mM.js
76 ms
277579766_5180551282011654_3521585556664000923_n.jpg
145 ms
1wEgRjtZ4_3.js
33 ms
UXtr_j2Fwe-.png
30 ms
3068d71730000000edaf.jpg
1973 ms
4d616487230000032fc8.png
2041 ms
gen_204
107 ms
pixel
42 ms
dv3.js
111 ms
window_focus.js
158 ms
qs_click_protection.js
185 ms
ufs_web_display.js
111 ms
pixel
39 ms
8199910165343492316
165 ms
abg_lite.js
148 ms
omrhp.js
149 ms
Q12zgMmT.js
160 ms
gen_204
307 ms
4d80e7e6ce00000418f9.png
2019 ms
47e8e8bc340000052d5d.png
2110 ms
pixel
371 ms
more3.png
2025 ms
ad
239 ms
task_icon_pc.png
1984 ms
62bHydCX.html
307 ms
activeview
181 ms
html_inpage_rendering_lib_200_280.js
141 ms
qrcode-01.jpg
1768 ms
nav-01.jpg
1838 ms
nav-02.jpg
1837 ms
nav-03.jpg
1938 ms
nav-04.jpg
1917 ms
nav-05.jpg
1853 ms
reactive_library.js
101 ms
ca-pub-5503686458589554
201 ms
bounce
75 ms
rum
108 ms
pHi-zHzKU2GlUHd7HF-1WSwsTvQuWvBiQ-SJiz2S1yc.js
11 ms
pixel
38 ms
11334516861712969031
35 ms
dc_oe=ChMI0sXBw4LlhwMVEhZoCB2dKhU0EAAYACDf9IloQhMIhvigw4LlhwMVZwFxCh3dhyMI;dc_eps=AHas8cAbmqkfgPJRAJK53XGDwpmjDLiCs0RAS3chvenjEZ8ARhCExGb_K96CCTkaytob10PueBgLVneoBbgayhOqwMw;met=1;×tamp=1723107198286;eid1=9;ecn1=1;etm1=0;
182 ms
pixel
70 ms
app-qrcode.svg
1667 ms
rum
84 ms
activeview
152 ms
ads
276 ms
14763004658117789537
75 ms
load_preloaded_resource.js
76 ms
abg_lite.js
74 ms
s
72 ms
8f33fcfe8f3fcce72fae06ada870480b.js
155 ms
fullscreen_api_adapter.js
85 ms
interstitial_ad_frame.js
89 ms
feedback_grey600_24dp.png
201 ms
settings_grey600_24dp.png
202 ms
gen_204
245 ms
pixel
189 ms
10549149356920051785
187 ms
237 ms
css
66 ms
pixel
62 ms
pixel
59 ms
activeview
89 ms
pixel
48 ms
setuid
46 ms
rum
48 ms
pixel
46 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
37 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
38 ms
rum
38 ms
uupon.tw 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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
uupon.tw 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
uupon.tw 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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uupon.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Uupon.tw 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.
uupon.tw
Open Graph data is detected on the main page of Uupon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: