2.6 sec in total
248 ms
1.9 sec
422 ms
Visit phpcs.com now to see the best up-to-date Phpcs content and also check out these interesting facts you probably never knew about phpcs.com
Le réseau CodeS-SourceS est une communauté de développeurs francophones de tout bord et de toute culture informatique. Cette communauté regroupe plus de 1 400 000 membres (avril 2009) à travers une id...
Visit phpcs.comWe analyzed Phpcs.com page load time and found that the first response time was 248 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
phpcs.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value5.1 s
26/100
25%
Value8.1 s
21/100
10%
Value5,010 ms
0/100
30%
Value0.227
55/100
15%
Value13.4 s
11/100
10%
248 ms
24 ms
169 ms
142 ms
121 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Phpcs.com, 7% (4 requests) were made to Ba.commentcamarche.net and 7% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (571 ms) relates to the external source Ba.commentcamarche.net.
Page size can be reduced by 517.6 kB (51%)
1.0 MB
497.2 kB
In fact, the total size of Phpcs.com 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 649.2 kB which makes up the majority of the site volume.
Potential reduce by 80.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. This page needs HTML code to be minified as it can gain 13.7 kB, which is 13% 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 80.0 kB or 74% of the original size.
Potential reduce by 24.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. Phpcs images are well optimized though.
Potential reduce by 413.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 413.2 kB or 64% of the original size.
Number of requests can be reduced by 30 (67%)
45
15
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phpcs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
php-5
248 ms
controltag
24 ms
1484253314@Top,Top1,Right,Position1,Position2,Position3,Position4,x01,x02,TopLeft
169 ms
jquery.min.js
142 ms
main
121 ms
css
48 ms
componentsCCM
82 ms
main
288 ms
jquery-ui.js
172 ms
core,lang.fr
488 ms
codesnippet
112 ms
ccmuievent,history
271 ms
univers
275 ms
app.bottom,start
111 ms
controltag.js.f8e94fa978cc2569e4b4423df4245d7e
54 ms
1484253314@Top,Top1,Right,Position1,Position2,Position3,Position4,x01,x02,TopLeft
165 ms
beacon.js
10 ms
gw.js
322 ms
ga.js
46 ms
analytics.js
98 ms
log_ccm_l.png
227 ms
8qG3CQSN-referencer-son-site-s-.png
223 ms
a40AilkU-admin3-s-.png
219 ms
log_cs_beta2.png
231 ms
shim.gif
39 ms
empty.gif
229 ms
bg_header.gif
203 ms
sprite_ico.png
269 ms
bg_nav.gif
239 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
124 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
128 ms
b9QBgL0iMZfDSpmcXcE8nCSLrGe-fkSRw2DeVgOoWcQ.woff
128 ms
b9QBgL0iMZfDSpmcXcE8nG9QJ2ZrAngtF2xl-5ukicw.ttf
121 ms
Zd2E9abXLFGSr9G3YK2MsFzqCfRpIA3W6ypxnPISCPA.woff
130 ms
Zd2E9abXLFGSr9G3YK2MsB43XjeME5heavxWqLE69Ro.ttf
122 ms
__utm.gif
55 ms
collect
43 ms
filehi-54ff5d2f
292 ms
sipatsymasaka-4ca5d64d
275 ms
bg_topcontributor.png
276 ms
user.png
280 ms
179148380.js
274 ms
resto_300x600.jpg
571 ms
bg_whiteOpa50.png
220 ms
sprite_footer_logos.png
221 ms
tag.js
273 ms
js.php
60 ms
css.php
59 ms
addthis_widget.js
55 ms
geste&v=
226 ms
logo_ccmbg.png
105 ms
boost
19 ms
300lo.json
86 ms
sh.07f0d9bf220d07a763adad1e.html
61 ms
phpcs.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
phpcs.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
phpcs.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phpcs.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Phpcs.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.
phpcs.com
Open Graph description is not detected on the main page of Phpcs. 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: