Tools & Wizards About Us
blog.phalcon.io screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

blog.phalcon.io

Phalcon Blog – We are an open source web framework for PHP delivered as a C extension offering high performance and lower resource consumption

Page Load Speed

1.5 sec in total

First Response

65 ms

Resources Loaded

499 ms

Page Rendered

980 ms

blog.phalcon.io screenshot

About Website

Click here to check amazing Blog Phalcon content for Indonesia. Otherwise, check out these important facts you probably never knew about blog.phalcon.io

We are an open source web framework for PHP delivered as a C extension offering high performance and lower resource consumption

Visit blog.phalcon.io

Key Findings

We analyzed Blog.phalcon.io page load time and found that the first response time was 65 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

blog.phalcon.io performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.149

76/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

blog.phalcon.io

65 ms

blog.phalcon.io

102 ms

main.min.css

112 ms

core-custom.css

156 ms

rocket-loader.min.js

8 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 53% of them (21 requests) were addressed to the original Blog.phalcon.io, 30% (12 requests) were made to Assets.phalcon.io and 5% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (220 ms) belongs to the original domain Blog.phalcon.io.

Page Optimization Overview & Recommendations

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

Content Size

3.8 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Blog.phalcon.io main page is 3.8 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. 40% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 40.4 kB

  • Original 50.5 kB
  • After minification 41.2 kB
  • After compression 10.1 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 9.3 kB, which is 18% 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 40.4 kB or 80% of the original size.

Image Optimization

-25%

Potential reduce by 941.2 kB

  • Original 3.8 MB
  • After minification 2.8 MB

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, Blog Phalcon needs image optimization as it can save up to 941.2 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 46 B

  • Original 4.2 kB
  • After minification 4.2 kB
  • After compression 4.2 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 5 (14%)

Requests Now

36

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blog.phalcon.io

blog.phalcon.io

65 ms

blog.phalcon.io

blog.phalcon.io

102 ms

main.min.css

main.min.css

112 ms

core-custom.css

core-custom.css

156 ms

rocket-loader.min.js

rocket-loader.min.js

8 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

38 ms

2024-07-10-phalcon-5.8.0-release.png

2024-07-10-phalcon-5.8.0-release.png

56 ms

2024-06-16-phalcon-swoole-htop.png

2024-06-16-phalcon-swoole-htop.png

51 ms

2024-06-16-phalcon-swoole-infra-history.jpg

2024-06-16-phalcon-swoole-infra-history.jpg

81 ms

2024-06-16-phalcon-swoole-ingress.png

2024-06-16-phalcon-swoole-ingress.png

83 ms

2024-06-16-phalcon-swoole-cpu.png

2024-06-16-phalcon-swoole-cpu.png

71 ms

2024-06-16-phalcon-swoole-ram.png

2024-06-16-phalcon-swoole-ram.png

111 ms

2024-06-16-phalcon-swoole-response-time.png

2024-06-16-phalcon-swoole-response-time.png

112 ms

2024-06-16-phalcon-swoole-pods.png

2024-06-16-phalcon-swoole-pods.png

112 ms

2024-06-16-phalcon-swoole-high-load-microservices.png

2024-06-16-phalcon-swoole-high-load-microservices.png

123 ms

2024-05-17-phalcon-5.7.0-release.png

2024-05-17-phalcon-5.7.0-release.png

130 ms

2024-03-14-phalcon-5.6.2-release.png

2024-03-14-phalcon-5.6.2-release.png

125 ms

money.jpg

money.jpg

178 ms

2024-02-08-phalcon-5.6.1-release.png

2024-02-08-phalcon-5.6.1-release.png

178 ms

2024-01-09-phalcon-5.6.0-release.png

2024-01-09-phalcon-5.6.0-release.png

190 ms

2017-12-24-christmas.jpg

2017-12-24-christmas.jpg

161 ms

2023-12-23-phalcon-hangout.png

2023-12-23-phalcon-hangout.png

165 ms

2023-10-25-phalcon-5.4.0-release.png

2023-10-25-phalcon-5.4.0-release.png

220 ms

mctekk-149x34.svg

mctekk-149x34.svg

139 ms

cloudflare.svg

cloudflare.svg

143 ms

abits-100x34.svg

abits-100x34.svg

144 ms

algolia-725x360.svg

algolia-725x360.svg

147 ms

crowdin.png

crowdin.png

141 ms

digitalocean.svg

digitalocean.svg

161 ms

postype.svg

postype.svg

166 ms

qodana.svg

qodana.svg

163 ms

css

css

37 ms

phalcon-logo-white-105x40.svg

phalcon-logo-white-105x40.svg

20 ms

arrow.svg

arrow.svg

15 ms

NaPecZTIAOhVxoMyOr9n_E7fdMPmCA.ttf

NaPecZTIAOhVxoMyOr9n_E7fdMPmCA.ttf

21 ms

js

js

71 ms

algoliasearchLite.min.js

algoliasearchLite.min.js

30 ms

HI_diYsKILxRpg3hIP6sJ7fM7PqPMcMnZFqUwX28DMyQtMlrSQ.ttf

HI_diYsKILxRpg3hIP6sJ7fM7PqPMcMnZFqUwX28DMyQtMlrSQ.ttf

6 ms

autocomplete.min.js

autocomplete.min.js

6 ms

search.js

search.js

56 ms

Accessibility Review

blog.phalcon.io accessibility score

98

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.

Best Practices

blog.phalcon.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

blog.phalcon.io SEO score

91

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

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 Blog.phalcon.io 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 Blog.phalcon.io 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

blog.phalcon.io

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