Access gri.net. Gri Teknoloji - Domain, Web Hosting, SSL Sertifikası

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

gri.net

184 ms

index.php

685 ms

gri.css

246 ms

jquery.min.js

319 ms

scripts.js

321 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 78% of them (54 requests) were addressed to the original Gri.net, 12% (8 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (711 ms) relates to the external source Paymendo.com.

Content Size

1.4 MB

After Optimization

969.3 kB

In fact, the total size of Gri.net main page is 1.4 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. 65% of websites need less resources to load. Images take 703.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 57.8 kB

Original 68.8 kB
After minification 47.0 kB
After compression 11.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 21.9 kB, which is 32% 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 57.8 kB or 84% of the original size.

Image Optimization

-18%

Potential reduce by 129.8 kB

Original 703.0 kB
After minification 573.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, Gri needs image optimization as it can save up to 129.8 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-40%

Potential reduce by 177.7 kB

Original 445.7 kB
After minification 386.8 kB
After compression 268.0 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 177.7 kB or 40% of the original size.

CSS Optimization

-42%

Potential reduce by 85.9 kB

Original 203.0 kB
After minification 196.5 kB
After compression 117.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. Gri.net needs all CSS files to be minified and compressed as it can save up to 85.9 kB or 42% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[role]s are not contained by their required parent element

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

TR
Language Claimed

TR
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gri.net can be misinterpreted by Google and other search engines. Our service has detected that Turkish is used on the page, and it matches the claimed language. Our system also found out that Gri.net 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

gri.net

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Gri Teknoloji - Domain, Web Hosting, SSL Sertifikası

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

gri.net

index.php

gri.css

jquery.min.js

scripts.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

gri.net

index.php

gri.css

jquery.min.js

scripts.js

jquery.mmenu.all.js

header.js

css2

campaign.js

system-core.js

bootstrap.bundle.min.js

jquery.colorbox-min.js

sweetalert2.all.min.js

typed.min.js

gauge.min.js

jquery.flexslider-min.js

alertify.js

icheck.js

punycode.js

swiper-bundle.min.js

velocity.min.js

search-product.js

jquery.inputmask.bundle.js

mixed.js

register-contracts.js

mobile-menu.css

flaticon.css

flexslider.css

component.css

alertify.css

fonts.css

j-forms.css

j-forms-grey.css

animate.min.css

hover-min.css

jquery.mmenu.all.css

colorbox.css

css

analytics.js

tm-banner-top.jpg

gri-white.svg

paymendo-logo-white.png

shipmendo-white-logo.png