Tools & Wizards About Us
firasblog.com screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

firasblog.com

Firas Blog | Pediatrics. Tech. Other stuff.

Page Load Speed

6.8 sec in total

First Response

2.2 sec

Resources Loaded

3.8 sec

Page Rendered

817 ms

firasblog.com screenshot

About Website

Visit firasblog.com now to see the best up-to-date Firas Blog content and also check out these interesting facts you probably never knew about firasblog.com

Short Quick Tips and Observations and Why-Nots

Visit firasblog.com

Key Findings

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

Performance Metrics

firasblog.com performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value1,040 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

firasblog.com

2215 ms

wp-emoji-release.min.js

57 ms

css

58 ms

style.css

86 ms

jetpack.css

139 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 23% of them (10 requests) were addressed to the original Firasblog.com, 11% (5 requests) were made to Pagead2.googlesyndication.com and 11% (5 requests) were made to I1.wp.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Firasblog.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 255.9 kB (26%)

Content Size

987.3 kB

After Optimization

731.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Firasblog.com main page is 987.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 573.0 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 53.8 kB

  • Original 75.4 kB
  • After minification 73.0 kB
  • After compression 21.7 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 53.8 kB or 71% of the original size.

Image Optimization

-1%

Potential reduce by 8.6 kB

  • Original 573.0 kB
  • After minification 564.5 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. Firas Blog images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 106.5 kB

  • Original 233.9 kB
  • After minification 232.2 kB
  • After compression 127.4 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 106.5 kB or 46% of the original size.

CSS Optimization

-83%

Potential reduce by 87.1 kB

  • Original 105.0 kB
  • After minification 93.9 kB
  • After compression 17.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. Firasblog.com needs all CSS files to be minified and compressed as it can save up to 87.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (49%)

Requests Now

41

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

firasblog.com

firasblog.com

2215 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

57 ms

css

css

58 ms

style.css

style.css

86 ms

jetpack.css

jetpack.css

139 ms

jquery.js

jquery.js

207 ms

jquery-migrate.min.js

jquery-migrate.min.js

112 ms

adsbygoogle.js

adsbygoogle.js

31 ms

photon.js

photon.js

92 ms

devicepx-jetpack.js

devicepx-jetpack.js

17 ms

gprofiles.js

gprofiles.js

56 ms

wpgroho.js

wpgroho.js

96 ms

navigation.js

navigation.js

179 ms

wp-embed.min.js

wp-embed.min.js

146 ms

e-201611.js

e-201611.js

18 ms

Make-PDF-Default.jpg

Make-PDF-Default.jpg

343 ms

D10W.jpg

D10W.jpg

252 ms

DeviceHeroImg.png

DeviceHeroImg.png

402 ms

happy-thanksgiving.jpg

happy-thanksgiving.jpg

411 ms

back-pocket-wallet.jpg

back-pocket-wallet.jpg

660 ms

FAAP.jpg

FAAP.jpg

1121 ms

iphone-double-tap-home-button.png

iphone-double-tap-home-button.png

1306 ms

iphone-home-screen-landscape.png

iphone-home-screen-landscape.png

880 ms

iPhone-Cleaner-01.jpg

iPhone-Cleaner-01.jpg

550 ms

ca-pub-9966299245533338.js

ca-pub-9966299245533338.js

288 ms

zrt_lookup.html

zrt_lookup.html

287 ms

show_ads_impl.js

show_ads_impl.js

196 ms

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

185 ms

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

251 ms

hovercard.css

hovercard.css

109 ms

services.css

services.css

121 ms

g.gif

g.gif

101 ms

ads

ads

235 ms

osd.js

osd.js

35 ms

ads

ads

326 ms

m_js_controller.js

m_js_controller.js

35 ms

abg.js

abg.js

54 ms

favicon

favicon

70 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

78 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

29 ms

s

s

59 ms

x_button_blue2.png

x_button_blue2.png

15 ms

16492755349931135507

16492755349931135507

31 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

11 ms

Accessibility Review

firasblog.com accessibility score

74

Accessibility Issues

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-*] attributes do not match their roles

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

Buttons do not have an accessible name

High

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

Best Practices

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

firasblog.com SEO score

92

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

firasblog.com

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