7.9 sec in total
532 ms
7.1 sec
227 ms
Click here to check amazing 77 Igg content. Otherwise, check out these important facts you probably never knew about 77igg.com
Visit 77igg.comWe analyzed 77igg.com page load time and found that the first response time was 532 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
77igg.com performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.274
44/100
15%
Value0
0/100
10%
532 ms
948 ms
478 ms
475 ms
972 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 83% of them (54 requests) were addressed to the original 77igg.com, 3% (2 requests) were made to Oz.cnzz.com and 3% (2 requests) were made to C.cnzz.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain 77igg.com.
Page size can be reduced by 237.0 kB (38%)
621.7 kB
384.7 kB
In fact, the total size of 77igg.com main page is 621.7 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. 35% of websites need less resources to load. Images take 343.4 kB which makes up the majority of the site volume.
Potential reduce by 26.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. 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 26.1 kB or 75% of the original size.
Potential reduce by 30.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. 77 Igg images are well optimized though.
Potential reduce by 122.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 122.4 kB or 73% of the original size.
Potential reduce by 57.6 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. 77igg.com needs all CSS files to be minified and compressed as it can save up to 57.6 kB or 77% of the original size.
Number of requests can be reduced by 25 (41%)
61
36
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 77 Igg. 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.
forum.php
532 ms
style_1_common.css
948 ms
style_1_forum_index.css
478 ms
style.css
475 ms
common.js
972 ms
forum.js
738 ms
logging.js
485 ms
ad.js
491 ms
discuz_tips.js
476 ms
banner.jpg
718 ms
switch_width.png
239 ms
banner.jpg
240 ms
logo.png
477 ms
tela.png
235 ms
linea.jpg
726 ms
xbt1.jpg
476 ms
9d660920fa17af1a62db283d948eaef7.jpg
954 ms
ff84e993cc140f42694e8122a45a543e.jpg
1204 ms
873aaa9913fcc6c79fdbd6e57b30ab8c.jpg
1662 ms
052dc9e78f90e88efacb90ccaa11fc85.jpg
1652 ms
efd6e17996d5966917bf16ccde05156a.jpg
1202 ms
39ad3b8a460db774ada3041f583fb98d.jpg
1457 ms
302d62262541d989a1beb04b34164e69.jpg
1673 ms
fab2d8488d4957662deef8a0c9e8e163.jpg
1687 ms
9b0585b990c26a1e84f388a60fc66229.jpg
1683 ms
a0d842e3e33103602f0becd31c065047.jpg
1946 ms
xbt2.jpg
1890 ms
xbt3.jpg
1898 ms
collapsed_no.gif
1914 ms
common_2_icon.jpg
1948 ms
common_39_icon.gif
1950 ms
common_40_icon.gif
2127 ms
common_42_icon.gif
2137 ms
hotel.jpg
2150 ms
vip.jpg
2192 ms
zjvip.jpg
2190 ms
common_45_icon.jpg
2192 ms
common_46_icon.jpg
2358 ms
online_admin.gif
2373 ms
online_supermod.gif
2390 ms
online_moderator.gif
2430 ms
online_member.gif
2431 ms
px.png
2417 ms
newarow.gif
2568 ms
pn.png
2585 ms
z_stat.php
761 ms
common_extra.js
2412 ms
nv.jpg
2443 ms
qmenu.png
2441 ms
nv_a.jpg
2208 ms
search.png
2361 ms
pt_item.png
2141 ms
chart.png
2169 ms
stat.htm
163 ms
core.php
917 ms
dot.gif
1968 ms
titlebg.jpg
1717 ms
9.gif
956 ms
scrolltop.png
1155 ms
z_stat.php
1658 ms
app.gif
1057 ms
stat.htm
162 ms
core.php
625 ms
9.gif
495 ms
app.gif
525 ms
77igg.com accessibility score
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
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
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.
77igg.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Missing source maps for large first-party JavaScript
77igg.com SEO score
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
N/A
N/A
BIG5
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 77igg.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that 77igg.com main page’s claimed encoding is big5. 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.
77igg.com
Open Graph description is not detected on the main page of 77 Igg. 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: