Tools & Wizards About Us
gign.lv screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

gign.lv

GIGN.lv - Team Fortress 2 / Counter strike community portal

Page Load Speed

14.2 sec in total

First Response

549 ms

Resources Loaded

7 sec

Page Rendered

6.6 sec

gign.lv screenshot

About Website

Click here to check amazing GIGN content for Latvia. Otherwise, check out these important facts you probably never knew about gign.lv

Team Fortress 2 and Counter Strike 1.6 / Source community portal with many servers, users forum, daily pictures, file downloads, clan war servers and much more.

Visit gign.lv

Key Findings

We analyzed Gign.lv page load time and found that the first response time was 549 ms and then it took 13.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

gign.lv performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value3,500 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.039

99/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

gign.lv

549 ms

style.css

199 ms

style.php

204 ms

menutabs.css

197 ms

jquery.lightbox-0.5.css

203 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 97% of them (75 requests) were addressed to the original Gign.lv, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Gign.lv.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.3 kB (26%)

Content Size

472.4 kB

After Optimization

350.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gign.lv main page is 472.4 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 276.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 34.6 kB

  • Original 42.6 kB
  • After minification 41.8 kB
  • After compression 8.0 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 34.6 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 4.0 kB

  • Original 276.2 kB
  • After minification 272.2 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. GIGN images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 52.2 kB

  • Original 114.6 kB
  • After minification 113.7 kB
  • After compression 62.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 52.2 kB or 46% of the original size.

CSS Optimization

-81%

Potential reduce by 31.6 kB

  • Original 39.0 kB
  • After minification 30.0 kB
  • After compression 7.5 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. Gign.lv needs all CSS files to be minified and compressed as it can save up to 31.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (61%)

Requests Now

74

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GIGN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

gign.lv

gign.lv

549 ms

style.css

style.css

199 ms

style.php

style.php

204 ms

menutabs.css

menutabs.css

197 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

203 ms

jquery-1.4.2.packed.js

jquery-1.4.2.packed.js

404 ms

j.packed.js

j.packed.js

375 ms

jx.packed.php

jx.packed.php

375 ms

sidebar_data.php

sidebar_data.php

374 ms

urchin.js

urchin.js

22 ms

bgcm.gif

bgcm.gif

542 ms

title.jpg

title.jpg

762 ms

lv.gif

lv.gif

666 ms

en.gif

en.gif

660 ms

loading_global.gif

loading_global.gif

651 ms

image_877.jpg

image_877.jpg

744 ms

icn_doc.gif

icn_doc.gif

680 ms

icn_comment.gif

icn_comment.gif

681 ms

image_875.jpg

image_875.jpg

1584 ms

image_873.jpg

image_873.jpg

723 ms

lv_ttn_viedoklis.gif

lv_ttn_viedoklis.gif

1548 ms

bal_0_1.gif

bal_0_1.gif

1582 ms

bal_0_2.gif

bal_0_2.gif

1361 ms

bal_0_3.gif

bal_0_3.gif

1302 ms

bal_1_1.gif

bal_1_1.gif

1525 ms

bal_1_2.gif

bal_1_2.gif

1534 ms

bal_1_3.gif

bal_1_3.gif

1533 ms

bal_2_1.gif

bal_2_1.gif

1533 ms

bal_2_2.gif

bal_2_2.gif

1533 ms

bal_2_3.gif

bal_2_3.gif

1533 ms

bal_3_1.gif

bal_3_1.gif

1737 ms

bal_3_2.gif

bal_3_2.gif

1733 ms

bal_3_3.gif

bal_3_3.gif

1710 ms

bal_4_1.gif

bal_4_1.gif

1711 ms

bal_4_2.gif

bal_4_2.gif

1702 ms

bal_4_3.gif

bal_4_3.gif

1702 ms

punkts.gif

punkts.gif

1703 ms

transp.gif

transp.gif

1703 ms

image_876.jpg

image_876.jpg

1753 ms

image_874.jpg

image_874.jpg

1800 ms

image_871.jpg

image_871.jpg

1800 ms

image_869.jpg

image_869.jpg

1801 ms

image_867.jpg

image_867.jpg

1801 ms

image_865.jpg

image_865.jpg

1800 ms

en_tt_bilde.gif

en_tt_bilde.gif

1801 ms

image_5127.jpg

image_5127.jpg

1300 ms

en_tt_online.gif

en_tt_online.gif

1298 ms

loading_br.gif

loading_br.gif

1359 ms

en_tt_teksts.gif

en_tt_teksts.gif

1508 ms

en_tt_flash.gif

en_tt_flash.gif

1445 ms

small_image_flash_1206545301_50.jpg

small_image_flash_1206545301_50.jpg

1444 ms

en_tt_members.gif

en_tt_members.gif

1432 ms

pieiet.gif

pieiet.gif

1412 ms

en_tt_live.gif

en_tt_live.gif

1401 ms

en_tt_live_tf2.gif

en_tt_live_tf2.gif

1728 ms

topnavig_bg.gif

topnavig_bg.gif

1507 ms

ttn_viedoklis_b.gif

ttn_viedoklis_b.gif

1507 ms

lin_punkt.gif

lin_punkt.gif

1505 ms

os-700.woff

os-700.woff

339 ms

os-300.woff

os-300.woff

340 ms

chatbox

chatbox

389 ms

no_scr.png

no_scr.png

231 ms

de_inferno_2x2.jpg

de_inferno_2x2.jpg

267 ms

map_bg.png

map_bg.png

267 ms

cs_italy.jpg

cs_italy.jpg

205 ms

cp_egypt_final.jpg

cp_egypt_final.jpg

266 ms

bg_bottom.gif

bg_bottom.gif

266 ms

__utm.gif

__utm.gif

645 ms

nobody.gif

nobody.gif

525 ms

laugh.gif

laugh.gif

526 ms

smile.gif

smile.gif

515 ms

admin.red.gif

admin.red.gif

500 ms

tongue.gif

tongue.gif

499 ms

ico_alise.jpg

ico_alise.jpg

499 ms

admin.blue.gif

admin.blue.gif

500 ms

ico_teddy.jpg

ico_teddy.jpg

599 ms

sad.gif

sad.gif

598 ms

Accessibility Review

gign.lv accessibility score

61

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

gign.lv best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

gign.lv SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    LV

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gign.lv can be misinterpreted by Google and other search engines. Our service has detected that Latvian/Lettish 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 Gign.lv 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.

Social Sharing Optimization

gign.lv

Open Graph description is not detected on the main page of GIGN. 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: