Tools & Wizards About Us
php.su screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

php.su

PHP, MySQL и другие веб-технологии

Page Load Speed

8 sec in total

First Response

478 ms

Resources Loaded

7.3 sec

Page Rendered

164 ms

php.su screenshot

About Website

Visit php.su now to see the best up-to-date PHP content for Ukraine and also check out these interesting facts you probably never knew about php.su

Портал по PHP, MySQL и другим веб-технологиям, Форум PHP программистов

Visit php.su

Key Findings

We analyzed Php.su page load time and found that the first response time was 478 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

php.su performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

81/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value2,270 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.086

93/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

php.su

478 ms

www.php.su

4187 ms

main.css

128 ms

main.js

252 ms

adsbygoogle.js

91 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 15% of them (12 requests) were addressed to the original Php.su, 11% (9 requests) were made to St6-21.vk.com and 10% (8 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Php.su.

Page Optimization Overview & Recommendations

Page size can be reduced by 164.5 kB (16%)

Content Size

1.0 MB

After Optimization

875.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Php.su main page is 1.0 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. 65% of websites need less resources to load. Javascripts take 751.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 70.6 kB

  • Original 85.5 kB
  • After minification 66.3 kB
  • After compression 14.9 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 19.2 kB, which is 22% 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 70.6 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 85 B

  • Original 60.4 kB
  • After minification 60.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. PHP images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 57.0 kB

  • Original 751.8 kB
  • After minification 751.8 kB
  • After compression 694.8 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.

CSS Optimization

-26%

Potential reduce by 36.8 kB

  • Original 142.3 kB
  • After minification 142.3 kB
  • After compression 105.5 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. Php.su needs all CSS files to be minified and compressed as it can save up to 36.8 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (81%)

Requests Now

69

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

php.su

php.su

478 ms

www.php.su

www.php.su

4187 ms

main.css

main.css

128 ms

main.js

main.js

252 ms

adsbygoogle.js

adsbygoogle.js

91 ms

ga.js

ga.js

36 ms

widgets.js

widgets.js

125 ms

openapi.js

openapi.js

242 ms

plusone.js

plusone.js

47 ms

hdrs.gif

hdrs.gif

174 ms

hdrm.gif

hdrm.gif

174 ms

nmdr.gif

nmdr.gif

266 ms

ndrs.gif

ndrs.gif

266 ms

button-php.gif

button-php.gif

266 ms

nginxpowered.png

nginxpowered.png

281 ms

button-css.png

button-css.png

280 ms

all.js

all.js

104 ms

__utm.gif

__utm.gif

99 ms

show_ads_impl.js

show_ads_impl.js

299 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

26 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

46 ms

fastbutton

fastbutton

62 ms

ftrs.gif

ftrs.gif

280 ms

aci.js

aci.js

675 ms

hit

hit

396 ms

all.js

all.js

43 ms

postmessageRelay

postmessageRelay

56 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

160 ms

developers.google.com

developers.google.com

1251 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

21 ms

rpc:shindig_random.js

rpc:shindig_random.js

10 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

mysql.png

mysql.png

439 ms

button-php.gif

button-php.gif

439 ms

button-css.png

button-css.png

424 ms

nginxpowered.png

nginxpowered.png

423 ms

settings

settings

135 ms

zrt_lookup.html

zrt_lookup.html

53 ms

ads

ads

448 ms

ads

ads

485 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

22 ms

hit

hit

508 ms

embeds

embeds

21 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ru.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ru.html

37 ms

counter2

counter2

252 ms

openapi.a2ed73393cad04481c1dfb3f7794921f.js

openapi.a2ed73393cad04481c1dfb3f7794921f.js

244 ms

reactive_library.js

reactive_library.js

149 ms

upload.gif

upload.gif

122 ms

widget_like.php

widget_like.php

475 ms

load_preloaded_resource.js

load_preloaded_resource.js

57 ms

icon.png

icon.png

17 ms

abg_lite.js

abg_lite.js

47 ms

s

s

26 ms

window_focus.js

window_focus.js

55 ms

qs_click_protection.js

qs_click_protection.js

59 ms

ufs_web_display.js

ufs_web_display.js

26 ms

bbcd6bf18c20baa1b2adeb195de9b551.js

bbcd6bf18c20baa1b2adeb195de9b551.js

266 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

250 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

255 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

243 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

250 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

251 ms

3957252553952054598

3957252553952054598

250 ms

css

css

139 ms

loader_nav210011395769_3.js

loader_nav210011395769_3.js

439 ms

lite.ca486089.css

lite.ca486089.css

806 ms

lang3_2.js

lang3_2.js

511 ms

c3d11fba.a7640b83.js

c3d11fba.a7640b83.js

663 ms

vkui.43318ab6.css

vkui.43318ab6.css

835 ms

xdm.js

xdm.js

662 ms

widgets.d2d14ebe.css

widgets.d2d14ebe.css

659 ms

al_like.js

al_like.js

667 ms

base.4d099727.css

base.4d099727.css

778 ms

activeview

activeview

189 ms

WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js

WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js

11 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

106 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

186 ms

lite.bcf10ece3464fec8b554bde483fa2494.js

lite.bcf10ece3464fec8b554bde483fa2494.js

489 ms

like_widget.png

like_widget.png

87 ms

upload.gif

upload.gif

89 ms

Accessibility Review

php.su accessibility score

77

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

php.su best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

php.su SEO score

69

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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Php.su can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Php.su main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

php.su

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