9.7 sec in total
611 ms
8.8 sec
272 ms
Click here to check amazing Megais content for Taiwan. Otherwise, check out these important facts you probably never knew about megais.com
提供網頁/網站設計、系統建置、網路行銷、媒體購買、多媒體開發、手機app服務開發,邁格多年來致力於提升創意品質,節省客戶時間成本;凝聚工作熱情,創造未來堅實團隊,以服務客戶為優先,在時間、成本、品質、創意等多方向,邁格總能做到面面俱到。
Visit megais.comWe analyzed Megais.com page load time and found that the first response time was 611 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.
megais.com performance score
611 ms
577 ms
386 ms
386 ms
387 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 98% of them (117 requests) were addressed to the original Megais.com, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Megais.com.
Page size can be reduced by 418.9 kB (19%)
2.2 MB
1.8 MB
In fact, the total size of Megais.com main page is 2.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. 40% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 75.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. 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 75.3 kB or 89% of the original size.
Potential reduce by 226.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. Obviously, Megais needs image optimization as it can save up to 226.7 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 100.7 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 100.7 kB or 64% of the original size.
Potential reduce by 16.2 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. Megais.com needs all CSS files to be minified and compressed as it can save up to 16.2 kB or 82% of the original size.
Number of requests can be reduced by 5 (4%)
118
113
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Megais. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
index.php
611 ms
megais2011.css
577 ms
icon_plurk.gif
386 ms
icon_facebook.gif
386 ms
icon_twitter.gif
387 ms
Pic_20150317040619.jpg
960 ms
Pic_20150317025625.jpg
954 ms
Pic_20150317023322.jpg
996 ms
Pic_20150317022108.jpg
1151 ms
Pic_20150317125526.jpg
998 ms
Pic_20150317124944.jpg
1153 ms
Pic_20150317123830.jpg
1340 ms
Pic_20150317123105.jpg
1346 ms
Pic_20150317122547.jpg
1380 ms
Pic_20150317121944.jpg
1195 ms
Pic_20150317120907.jpg
1344 ms
Pic_20150317120107.jpg
1349 ms
Pic_20150317114734.jpg
1533 ms
Pic_20150317113525.jpg
1346 ms
Pic_20150317113224.jpg
1575 ms
Pic_20150306073529.jpg
1726 ms
Pic_20150306073051.jpg
1730 ms
Pic_20150306072739.jpg
1732 ms
Pic_20150306071658.jpg
2181 ms
Pic_20150306071017.jpg
1918 ms
Pic_20150306070528.jpg
1963 ms
Pic_20150306065913.jpg
2296 ms
Pic_20150306064200.jpg
2110 ms
Pic_20150306063735.jpg
1926 ms
Pic_20150306055954.jpg
2526 ms
Pic_20150306055520.jpg
2305 ms
Pic_20150306055252.jpg
2986 ms
Pic_20150306054545.jpg
2300 ms
Pic_20150306054002.jpg
2751 ms
Pic_20150306053612.png
3248 ms
Pic_20150306052907.jpg
2491 ms
jquery-1.7.1.min.js
2510 ms
jQuerySet.js
2493 ms
jquery.accessible-news-slider2.js
2527 ms
thickbox.js
2686 ms
jquery.accessible-news-slider2.css
2514 ms
thickbox.css
2152 ms
jquery.nivo.slider.js
2223 ms
Pic_20150306052432.jpg
2457 ms
Pic_20150306051938.jpg
2282 ms
Pic_20150306051005.jpg
2527 ms
Pic_20150306050332.jpg
2527 ms
Pic_20150306045439.jpg
2184 ms
Pic_20150306044917.jpg
2126 ms
Pic_20150306044253.jpg
2440 ms
Pic_20150306043706.jpg
2110 ms
Pic_20150306043127.jpg
2127 ms
Pic_20150306042659.jpg
2560 ms
Pic_20150306042033.jpg
2270 ms
Pic_20150306041634.jpg
2135 ms
Pic_20150306041037.jpg
2489 ms
Pic_20150306040308.jpg
2153 ms
Pic_20150306035201.jpg
2478 ms
Pic_20150306032239.jpg
2297 ms
Pic_20130729054309.jpg
2135 ms
Pic_20130704110226.jpg
2334 ms
Pic_20130703064717.jpg
2515 ms
Pic_20130704112321.jpg
2112 ms
Pic_20130520120441.png
3023 ms
Pic_20130514064348.png
3337 ms
Pic_20130704122739.jpg
2286 ms
Pic_20130515053622.png
2107 ms
Pic_20130327110138.jpg
2152 ms
Pic_20130327123905.jpg
2081 ms
Pic_20130325043851.jpg
2593 ms
Pic_20130325122043.jpg
2272 ms
Pic_20130325112601.jpg
2081 ms
Pic_20130325115542.jpg
2280 ms
Pic_20120824022113.jpg
2115 ms
Pic_20120824022755.jpg
2456 ms
ga.js
64 ms
Pic_20120704011901.jpg
2199 ms
Pic_20120622053805.jpg
2427 ms
__utm.gif
13 ms
Pic_20120622053013.jpg
2348 ms
Pic_20120622053303.jpg
3074 ms
Pic_20120423074445.jpg
2413 ms
Pic_20120403080801.jpg
3256 ms
Pic_20120405063248.png
2291 ms
Pic_20120210104222.jpg
2470 ms
Pic_20120119055749.jpg
2317 ms
Pic_20120119052055.jpg
2737 ms
Pic_20120119064204.jpg
2560 ms
Pic_20120119060148.jpg
2473 ms
Pic_20111123072616.jpg
2552 ms
Pic_20111108033822.jpg
2508 ms
Pic_20111028071926.gif
2571 ms
Pic_20110913035006.jpg
2468 ms
Pic_20111125035227.jpg
3066 ms
Pic_20121116073135.jpg
2537 ms
Pic_20111125071625.jpg
2732 ms
Pic_20110810013125.jpg
2556 ms
Pic_20130716030018.jpg
2334 ms
Pic_20110609030310.jpg
3056 ms
Pic_20110506074011.jpg
2473 ms
Pic_20110506050113.jpg
2540 ms
Pic_20110506051817.jpg
2526 ms
Pic_20110131101016.jpg
2339 ms
Pic_20110131101928.jpg
2751 ms
Pic_20110131102849.jpg
2473 ms
Pic_20111125072623.jpg
2535 ms
Pic_20110131114825.jpg
2573 ms
Pic_20110128070043.jpg
2389 ms
Pic_20110128070747.jpg
2276 ms
Pic_20110128071755.jpg
2667 ms
Pic_20110128072409.jpg
2493 ms
Pic_20100420071510.jpg
2638 ms
body_bg.gif
2199 ms
portfolio_bg.gif
2200 ms
arrow_back.gif
2326 ms
arrow_next.gif
2172 ms
likeTitle.gif
2140 ms
facebook.gif
2225 ms
loadingAnimation.gif
2164 ms
megais.com SEO score
ZH
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Megais.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Megais.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.
megais.com
Open Graph description is not detected on the main page of Megais. 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: