Access asksaygin.com. Your International DJ SAY-G

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value4,410 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.16

73/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

167 ms

1381 ms

analytics.js

250 ms

wp-emoji-release.min.js

228 ms

otw-grid.css

319 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Asksaygin.com, 5% (7 requests) were made to Fonts.gstatic.com and 5% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Startuphero.com.

Content Size

1.2 MB

After Optimization

470.5 kB

In fact, the total size of Asksaygin.com main page is 1.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 693.3 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 157.6 kB

Original 206.1 kB
After minification 205.4 kB
After compression 48.5 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 157.6 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 4 B

Original 21.4 kB
After minification 21.4 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. Ask SAY Gin images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 420.5 kB

Original 693.3 kB
After minification 679.0 kB
After compression 272.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 420.5 kB or 61% of the original size.

CSS Optimization

-60%

Potential reduce by 192.2 kB

Original 320.0 kB
After minification 307.5 kB
After compression 127.8 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. Asksaygin.com needs all CSS files to be minified and compressed as it can save up to 192.2 kB or 60% of the original size.

Requests Now

118

After Optimization

The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ask SAY Gin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 74 to 1 for JavaScripts and from 30 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

[aria-*] attributes do not match their roles

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

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

High

Page is blocked from indexing

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

Language and Encoding

Language Detected

N/A
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Asksaygin.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), while the claimed language is English. Our system also found out that Asksaygin.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.

Social Sharing Optimization

Open Graph data is detected on the main page of Ask SAY Gin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: