Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

glx.ir

گوشی های جی ال ایکس GLX Mobile

Page Load Speed

31.5 sec in total

First Response

1.2 sec

Resources Loaded

29.8 sec

Page Rendered

545 ms

glx.ir screenshot

About Website

Welcome to glx.ir homepage info - get ready to check GLX best content for Iran right away, or after learning these important things about glx.ir

Visit glx.ir

Key Findings

We analyzed Glx.ir page load time and found that the first response time was 1.2 sec and then it took 30.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 19 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

glx.ir performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value3,270 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.291

41/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

glx.ir

1224 ms

base.min.css

3264 ms

index.min.css

1496 ms

screen.css

1852 ms

base.min.js

5648 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 95% of them (62 requests) were addressed to the original Glx.ir, 2% (1 request) were made to Trustseal.enamad.ir and 2% (1 request) were made to Userid.xiaomi.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Userid.xiaomi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 969.1 kB (50%)

Content Size

2.0 MB

After Optimization

988.2 kB

In fact, the total size of Glx.ir main page is 2.0 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. 15% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 45.0 kB

  • Original 51.0 kB
  • After minification 30.7 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 20.3 kB, which is 40% 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 45.0 kB or 88% of the original size.

Image Optimization

-31%

Potential reduce by 377.1 kB

  • Original 1.2 MB
  • After minification 829.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. Obviously, GLX needs image optimization as it can save up to 377.1 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-78%

Potential reduce by 331.7 kB

  • Original 427.5 kB
  • After minification 320.0 kB
  • After compression 95.8 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 331.7 kB or 78% of the original size.

CSS Optimization

-79%

Potential reduce by 215.4 kB

  • Original 272.5 kB
  • After minification 238.9 kB
  • After compression 57.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. Glx.ir needs all CSS files to be minified and compressed as it can save up to 215.4 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (24%)

Requests Now

42

After Optimization

32

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

Accessibility Review

glx.ir accessibility score

72

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.

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

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

glx.ir best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

glx.ir SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document doesn't use legible font sizes

Language and Encoding

  • Language Detected

    FA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

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