Tools & Wizards About Us
frankom.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

frankom.com

فرانكوم

Page Load Speed

3.8 sec in total

First Response

734 ms

Resources Loaded

2.1 sec

Page Rendered

923 ms

frankom.com screenshot

About Website

Welcome to frankom.com homepage info - get ready to check Frankom best content for Kuwait right away, or after learning these important things about frankom.com

Visit frankom.com

Key Findings

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

Performance Metrics

frankom.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value3,690 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value23.8 s

1/100

10%

Network Requests Diagram

www.frankom.com

734 ms

style.css

246 ms

styles.css

168 ms

genericons.css

242 ms

jetpack.css

327 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 25% of them (17 requests) were addressed to the original Frankom.com, 16% (11 requests) were made to Pixel.wp.com and 14% (10 requests) were made to Graph.facebook.com. The less responsive or slowest element that took the longest time to load (734 ms) belongs to the original domain Frankom.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 608.0 kB (48%)

Content Size

1.3 MB

After Optimization

665.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Frankom.com main page is 1.3 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. 60% of websites need less resources to load. Images take 438.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 51.2 kB

  • Original 61.2 kB
  • After minification 58.3 kB
  • After compression 10.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 51.2 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 816 B

  • Original 438.5 kB
  • After minification 437.7 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. Frankom images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 264.9 kB

  • Original 408.3 kB
  • After minification 400.5 kB
  • After compression 143.5 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 264.9 kB or 65% of the original size.

CSS Optimization

-80%

Potential reduce by 291.2 kB

  • Original 365.4 kB
  • After minification 354.9 kB
  • After compression 74.3 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. Frankom.com needs all CSS files to be minified and compressed as it can save up to 291.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (52%)

Requests Now

62

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.frankom.com

www.frankom.com

734 ms

style.css

style.css

246 ms

styles.css

styles.css

168 ms

genericons.css

genericons.css

242 ms

jetpack.css

jetpack.css

327 ms

jquery.js

jquery.js

407 ms

jquery-migrate.min.js

jquery-migrate.min.js

319 ms

photon.js

photon.js

163 ms

jquery.form.min.js

jquery.form.min.js

177 ms

scripts.js

scripts.js

244 ms

devicepx-jetpack.js

devicepx-jetpack.js

59 ms

gprofiles.js

gprofiles.js

61 ms

wpgroho.js

wpgroho.js

351 ms

wp-embed.min.js

wp-embed.min.js

354 ms

sharing.js

sharing.js

353 ms

e-201609.js

e-201609.js

7 ms

droidarabickufi.css

droidarabickufi.css

24 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

430 ms

Screen-Shot-2016-02-29-at-9.33.32-AM.png

Screen-Shot-2016-02-29-at-9.33.32-AM.png

87 ms

NYWsQC3kCVA

NYWsQC3kCVA

219 ms

cRjvF6R3lZs

cRjvF6R3lZs

221 ms

top100.jpg

top100.jpg

80 ms

img_5359.jpg

img_5359.jpg

76 ms

frankomheader.jpg

frankomheader.jpg

340 ms

loading.gif

loading.gif

207 ms

img_5469.jpg

img_5469.jpg

364 ms

img_5468.jpg

img_5468.jpg

364 ms

GettyImages-123090026.jpg

GettyImages-123090026.jpg

364 ms

Capture.jpg

Capture.jpg

363 ms

img_4990-1.jpg

img_4990-1.jpg

68 ms

img_4989-1.jpg

img_4989-1.jpg

365 ms

wp-1455419118851.jpg

wp-1455419118851.jpg

364 ms

wp-1455419118321.jpg

wp-1455419118321.jpg

66 ms

img_5360.jpg

img_5360.jpg

64 ms

DroidKufi-Regular.woff

DroidKufi-Regular.woff

41 ms

DroidKufi-Bold.woff

DroidKufi-Bold.woff

126 ms

Genericons.svg

Genericons.svg

380 ms

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

3 ms

ajs.php

ajs.php

26 ms

hovercard.css

hovercard.css

164 ms

services.css

services.css

166 ms

graph.facebook.com

graph.facebook.com

187 ms

g.gif

g.gif

29 ms

graph.facebook.com

graph.facebook.com

247 ms

graph.facebook.com

graph.facebook.com

252 ms

graph.facebook.com

graph.facebook.com

253 ms

graph.facebook.com

graph.facebook.com

268 ms

graph.facebook.com

graph.facebook.com

258 ms

graph.facebook.com

graph.facebook.com

251 ms

graph.facebook.com

graph.facebook.com

330 ms

graph.facebook.com

graph.facebook.com

330 ms

graph.facebook.com

graph.facebook.com

329 ms

g.gif

g.gif

135 ms

g.gif

g.gif

136 ms

g.gif

g.gif

134 ms

g.gif

g.gif

135 ms

g.gif

g.gif

137 ms

g.gif

g.gif

135 ms

g.gif

g.gif

138 ms

g.gif

g.gif

138 ms

g.gif

g.gif

138 ms

www-embed-player-vflZsBgOl.css

www-embed-player-vflZsBgOl.css

173 ms

www-embed-player.js

www-embed-player.js

189 ms

g.gif

g.gif

35 ms

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

68 ms

ad_status.js

ad_status.js

68 ms

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

61 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

90 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

90 ms

Accessibility Review

frankom.com accessibility score

92

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

High

Links do not have a discernible name

Best Practices

frankom.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

SEO Factors

frankom.com SEO score

79

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

High

Page is blocked from indexing

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 uses legible font sizes

Language and Encoding

  • Language Detected

    AR

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

frankom.com

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