4.2 sec in total
261 ms
3.5 sec
441 ms
Visit story.gogoro.com now to see the best up-to-date Story Gogoro content for Taiwan and also check out these interesting facts you probably never knew about story.gogoro.com
Our society is at a tipping point. We need bold solutions and a mindset for change for the next generation. It’s time to rethink how the growing cities of tomorrow distribute, manage and experience en...
Visit story.gogoro.comWe analyzed Story.gogoro.com page load time and found that the first response time was 261 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
story.gogoro.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value16.0 s
0/100
25%
Value7.0 s
32/100
10%
Value320 ms
76/100
30%
Value0.08
94/100
15%
Value14.0 s
10/100
10%
261 ms
34 ms
32 ms
29 ms
61 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Story.gogoro.com, 20% (17 requests) were made to Static.tumblr.com and 18% (16 requests) were made to 40.media.tumblr.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Staticxx.facebook.com.
Page size can be reduced by 626.0 kB (13%)
4.7 MB
4.0 MB
In fact, the total size of Story.gogoro.com main page is 4.7 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. 85% 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 3.9 MB which makes up the majority of the site volume.
Potential reduce by 197.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. This page needs HTML code to be minified as it can gain 34.6 kB, which is 15% 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 197.6 kB or 87% of the original size.
Potential reduce by 68.1 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. Story Gogoro images are well optimized though.
Potential reduce by 359.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 359.4 kB or 65% of the original size.
Potential reduce by 836 B
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. Story.gogoro.com needs all CSS files to be minified and compressed as it can save up to 836 B or 62% of the original size.
Number of requests can be reduced by 24 (29%)
84
60
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Story Gogoro. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
story.gogoro.com
261 ms
pre_tumblelog.js
34 ms
reset.css
32 ms
tumblelog_post_message_queue.js
29 ms
jquery.min.js
61 ms
wookmark.min.js
98 ms
clamp.js
94 ms
infinitescrolling.js
98 ms
index.js
71 ms
138624017765
62 ms
sdk.js
692 ms
like_iframe.html
51 ms
tumblr_inline_o49tvxMjVX1tanzsd_500.jpg
53 ms
tumblr_inline_o3nlgrcMBx1tanzsd_500.jpg
507 ms
tumblr_inline_o3gkdf3xuK1tanzsd_500.jpg
580 ms
tumblr_inline_nyd47leG9A1tanzsd_540.gif
43 ms
tumblr_inline_o3epomUpsJ1tanzsd_500.jpg
674 ms
tumblr_inline_nygz2zzh941tanzsd_500.jpg
680 ms
tumblr_inline_nyeme174Vu1tanzsd_500.jpg
677 ms
tumblr_inline_nydazzquCV1tanzsd_500.jpg
674 ms
tumblr_inline_nyd8x1tKGQ1tanzsd_500.jpg
678 ms
tumblr_inline_nyaz2cCqrC1tanzsd_500.jpg
679 ms
tumblr_static_6w2wnee9zw8wgss4kskc08wgo_2048_v2.jpg
564 ms
facebook_btn.png
436 ms
youtube_btn.png
488 ms
hashtag_btn.png
489 ms
insta_btn.png
489 ms
main_title.png
489 ms
main_desc.png
488 ms
scroll_icon.png
490 ms
logo.png
560 ms
block_facebook.png
559 ms
block_twitter.png
491 ms
modal_left.png
560 ms
modal_right.png
559 ms
analytics.js
437 ms
impixu
513 ms
impixu
133 ms
analytics.html
234 ms
login_check.html
122 ms
collect
120 ms
avatar_3d0602e34e43_40.png
96 ms
iframe_logo.png
34 ms
rapid-3.36.js
59 ms
rapidworker-1.2.js
89 ms
collect
93 ms
84 ms
xd_arbiter.php
241 ms
xd_arbiter.php
1664 ms
ga.js
70 ms
analytics.js
40 ms
cs.js
48 ms
yql
1486 ms
__utm.gif
17 ms
2
1510 ms
cedexis.radar.js
1312 ms
jfont.woff
694 ms
tumblr_inline_ny98zeM6BE1tanzsd_500.jpg
133 ms
tumblr_inline_ny0q7ynLA31tanzsd_500.jpg
447 ms
tumblr_inline_nxyveymyyp1tanzsd_500.jpg
76 ms
tumblr_inline_nxdtabLRW01tanzsd_500.jpg
116 ms
tumblr_inline_nxdt4nDp8s1tanzsd_500.jpg
464 ms
tumblr_inline_nx8j6ltryi1tanzsd_500.jpg
203 ms
tumblr_inline_nx8j9g6DgJ1tanzsd_500.jpg
202 ms
tumblr_inline_nxfp36rPyI1tanzsd_500.jpg
60 ms
tumblr_inline_nx8jdlcjM71tanzsd_500.jpg
59 ms
tumblr_inline_nx8idt9vJR1tanzsd_500.jpg
238 ms
3
269 ms
__utm.gif
31 ms
tumblr_inline_nx8fe2zdeI1tanzsd_500.jpg
100 ms
tumblr_inline_nx161cOL3q1tanzsd_500.jpg
131 ms
tumblr_inline_nwz08oTeB51tanzsd_500.jpg
246 ms
tumblr_inline_nwz0llVmbd1tanzsd_500.jpg
400 ms
tumblr_inline_nwmoprAqAh1tanzsd_500.jpg
130 ms
tumblr_inline_nwmo8bYDYL1tanzsd_500.jpg
131 ms
tumblr_inline_nwvc45ql7G1tanzsd_500.jpg
302 ms
tumblr_inline_nwvk80Ld6d1tanzsd_500.jpg
206 ms
tumblr_inline_nwz09dQhtB1tanzsd_500.jpg
267 ms
tumblr_inline_nx160vetuj1tanzsd_500.jpg
77 ms
tumblr_inline_nx12f9seqs1tanzsd_500.jpg
77 ms
tumblr_inline_nwz12rl2ty1tanzsd_500.jpg
80 ms
tumblr_inline_nwvc2s3Pen1tanzsd_500.jpg
74 ms
tumblr_inline_nwz08xNJ0Y1tanzsd_500.jpg
90 ms
tumblr_inline_nwz0eaOXK91tanzsd_500.jpg
77 ms
tumblr_inline_nwnlz1eMdR1tanzsd_500.jpg
89 ms
tumblr_inline_nwmofaoYDU1tanzsd_500.jpg
94 ms
__utm.gif
13 ms
story.gogoro.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
Image elements do not have [alt] attributes
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.
story.gogoro.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
story.gogoro.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Story.gogoro.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Story.gogoro.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.
story.gogoro.com
Open Graph description is not detected on the main page of Story Gogoro. 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: