Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

filegap.com

FileRun :: Login

Page Load Speed

9.3 sec in total

First Response

3.2 sec

Resources Loaded

5.6 sec

Page Rendered

440 ms

filegap.com screenshot

About Website

Visit filegap.com now to see the best up-to-date File Gap content for Pakistan and also check out these interesting facts you probably never knew about filegap.com

Softwares Free Download

Visit filegap.com

Key Findings

We analyzed Filegap.com page load time and found that the first response time was 3.2 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

filegap.com performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value850 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

filegap.com

3241 ms

bootstrap.min.css

218 ms

font-awesome.min.css

135 ms

style.css

134 ms

responsive.css

93 ms

Our browser made a total of 203 requests to load all elements on the main page. We found that 56% of them (113 requests) were addressed to the original Filegap.com, 3% (7 requests) were made to Googleads.g.doubleclick.net and 3% (7 requests) were made to Px.owneriq.net. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Filegap.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (61%)

Content Size

1.9 MB

After Optimization

744.9 kB

In fact, the total size of Filegap.com main page is 1.9 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. 75% 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 248.1 kB

  • Original 276.4 kB
  • After minification 272.6 kB
  • After compression 28.3 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 248.1 kB or 90% of the original size.

Image Optimization

-7%

Potential reduce by 22.2 kB

  • Original 339.5 kB
  • After minification 317.3 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. File Gap images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 717.5 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 360.9 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 717.5 kB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 174.8 kB

  • Original 213.2 kB
  • After minification 206.5 kB
  • After compression 38.4 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. Filegap.com needs all CSS files to be minified and compressed as it can save up to 174.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 88 (48%)

Requests Now

184

After Optimization

96

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

Accessibility Review

filegap.com accessibility score

67

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.

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

<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

High

<html> element does not have a [lang] attribute

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

filegap.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

filegap.com SEO score

73

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

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

    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 Filegap.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 Filegap.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 File Gap. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: