3.7 sec in total
261 ms
3.1 sec
389 ms
Click here to check amazing Le Phoceen content. Otherwise, check out these important facts you probably never knew about lephoceen.com
OM Marseille, retrouvez toute l'information, le mercato, réagissez à l'actualité, participez au forum, notez les joueurs et retrouvez nos vidéos sur le Phocéen TV.
Visit lephoceen.comWe analyzed Lephoceen.com page load time and found that the first response time was 261 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
lephoceen.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value8.9 s
1/100
25%
Value11.0 s
6/100
10%
Value1,890 ms
9/100
30%
Value0.133
81/100
15%
Value18.7 s
3/100
10%
261 ms
448 ms
320 ms
553 ms
178 ms
Our browser made a total of 235 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Lephoceen.com, 20% (48 requests) were made to Static.lephoceen.net and 19% (44 requests) were made to Pixel.rubiconproject.com. The less responsive or slowest element that took the longest time to load (736 ms) relates to the external source Static.lephoceen.net.
Page size can be reduced by 1.3 MB (50%)
2.7 MB
1.3 MB
In fact, the total size of Lephoceen.com main page is 2.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 229.2 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 229.2 kB or 87% of the original size.
Potential reduce by 80.6 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. Le Phoceen images are well optimized though.
Potential reduce by 914.7 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 914.7 kB or 69% of the original size.
Potential reduce by 109.2 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. Lephoceen.com needs all CSS files to be minified and compressed as it can save up to 109.2 kB or 82% of the original size.
Number of requests can be reduced by 137 (67%)
204
67
The browser has sent 204 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Le Phoceen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and as a result speed up the page load time.
lephoceen.com
261 ms
www.lephoceen.fr
448 ms
style.min.css
320 ms
main.min.js
553 ms
no
178 ms
no
169 ms
xtcore.js
172 ms
show30.asp
87 ms
controltag
27 ms
loader.js
16 ms
34c4a38a656e09fa0f17243adc29a14f.png
85 ms
3db1382458420fc4f3a7032d99f4ff3a.png
83 ms
ecf07b4d19e0a03e0ae205d040f77b88.png
84 ms
50fe0bc396c71e0daf2d42d54303bbc6.png
158 ms
3d7d3ef08157109cd7416b09c267f603.png
162 ms
fb4756ce6b5ac85f167f0c66ccc3fa7a.png
161 ms
62d87a55915174d82801374cd5a814fa.jpg
399 ms
89c6d4ebc814975f8c64da2f4459c261.jpg
366 ms
2c9ddeb09aed4c17b6cb6c8f6a5c91d3.jpg
367 ms
67b6ec745b294d9188960dab9d543baf.jpg
258 ms
1a11347184a4ab4e56b2c612f883e8b7.jpg
364 ms
deb3fdc11d8b057b00530e1403a4b375.jpg
391 ms
6ac6ac81c6252a412d87481d236b3968.jpg
363 ms
e1dc6a793de02cf5fdc9648b6f87720c.jpg
393 ms
ee0a33f65e657a1d15924a120365d8b5.jpg
562 ms
b1040e45227866bf33436bc34255b2fc.jpg
398 ms
7e09215f363a1143cad68d2b12bf68af.jpg
411 ms
7fc16c46742883568b37472d0caae5ef.jpg
561 ms
3fc3d67f755f7192b3a2e2cb7bd8f20a.jpg
562 ms
3d794577b49f6551ff07a2f6205dba22.jpg
563 ms
e416faf4277cb9805591f1dc4bba43cf.jpg
563 ms
0493b16ce60364a9006ab9a115ebac03.jpg
564 ms
3367124dceca7ce449d786efa3b60ec1.jpg
567 ms
cab815bf2160501db6ee812305f24ff3.jpg
567 ms
b4639e977f194b57ab730f99f880c3b3.jpg
568 ms
2239dd9f4d6125b629fa33dc4837f741.jpg
590 ms
30de567c627a19fb959613b55f185e31.jpg
591 ms
8cab45ff06f3725c3b0d23cedad27e7f.jpg
598 ms
2f3aa7d5e94939b0fe09e2389d88a35c.jpg
643 ms
fb29304da9fada7fe2c200cbd87c6bdf.jpg
643 ms
1fec9f56aacd765c60c199afea267791.jpg
643 ms
bda493d7f2eec4bfaa138e206f160a2f.png
662 ms
2d49f9c5a90b594ae82673eda0b3f94a.png
663 ms
eb9cd8c922d163a618ed714e100d4451.png
683 ms
c46834d1b97f42895412620ebef538f1.png
736 ms
rc
224 ms
88503df7a0b22869a035a72b07995589.png
735 ms
impl.200-RELEASE.js
11 ms
beacon.js
8 ms
controltag.js.f8e94fa978cc2569e4b4423df4245d7e
32 ms
bouton_iphone_300.jpg
657 ms
bouton_android_300.jpg
669 ms
8cc47f2effdd2da51583c50f4fd4e8b6.png
668 ms
70d7ee3fde15da21560801b0613f728c.png
594 ms
e037279dcc93961006dab2743112783b.png
630 ms
c820c8abc3b1431adeee1226aa64a5d0.png
624 ms
data-registering
46 ms
gpt.js
28 ms
ddf34f3d937d8650c1410c65dd0e82e6.png
531 ms
pubads_impl_82.js
11 ms
jsinfo.asp
99 ms
2015_INT_bonus_600x35.jpg
78 ms
ads
197 ms
container.html
26 ms
ionicons.ttf
700 ms
c6d656f030294815197e787abf32b5c8.jpg
467 ms
sas-browser.js
15 ms
sas-dom.js
4 ms
sas-banner-2.2.js
4 ms
index.html
15 ms
edge.6.0.0.min.js
17 ms
sas-clicktag-2.1.js
133 ms
jquery-1.11.3.min.js
216 ms
TweenMax.min.js
172 ms
analytics.js
104 ms
statistic
239 ms
measure.min.js
43 ms
ads.min.js
45 ms
9585.js
38 ms
adtag.js
43 ms
300x250_Poker2_edge.js
56 ms
osd.js
32 ms
collect
41 ms
sync
44 ms
sync
41 ms
i
25 ms
i
23 ms
textlink-ads.jpg
17 ms
textlink-ads.jpg
15 ms
a.js
40 ms
bounce
33 ms
266382-57.js
94 ms
222190-10.js
109 ms
bounce
45 ms
300x250_Poker2_edge.js
37 ms
sync
88 ms
BCKGRND.jpg
25 ms
sync
19 ms
sync
9 ms
221794-58.js
68 ms
222192-15.js
71 ms
sync
10 ms
sync
9 ms
221796-2.js
112 ms
222200-15.js
63 ms
0RaXcM1FOu_395154613.html
13 ms
emily.html
24 ms
emily.html
19 ms
emily.html
20 ms
adServer.bs
134 ms
creative_add_on.js
94 ms
emily.html
22 ms
json
39 ms
tap.php
19 ms
sync
25 ms
hit.xiti
252 ms
222182-2.js
119 ms
3aadbb71016ecd7a194bbe2791777e9a.png
21 ms
pires-buts-rates-football.jpg
83 ms
cebf06e2eb6e7fb2d0285a1a6b1de6c9.png
12 ms
356ce9b35788683bb90a60811019e89e.png
22 ms
F4-img-2_1.jpg
37 ms
cms-2c.html
44 ms
show_ads.js
22 ms
2964
67 ms
Pug
44 ms
rum
61 ms
sync
36 ms
tap.php
30 ms
ca-pub-3909565475304434.js
142 ms
zrt_lookup.html
176 ms
show_ads_impl.js
87 ms
sd
50 ms
demconf.jpg
44 ms
pixel
170 ms
pixel.gif
141 ms
385636.gif
63 ms
emily.html
59 ms
rum
89 ms
check
112 ms
emily.html
79 ms
pixel.htm
118 ms
emily.html
70 ms
ads
292 ms
channels.js
48 ms
emily.html
37 ms
osd.js
42 ms
m.gif
31 ms
cms-2c-rubicon.html
50 ms
tap.php
66 ms
rs
37 ms
match-result
98 ms
rubicon
31 ms
pixel
35 ms
rubicon.ashx
93 ms
rc
41 ms
ddc.htm
51 ms
m_yahoo.gif
29 ms
rubicon
27 ms
tap.php
13 ms
tap.php
26 ms
tap.php
42 ms
tap.php
27 ms
rubicon
49 ms
cs
235 ms
pixelpush
63 ms
GenericUserSync.ashx
53 ms
325 ms
rb_match
50 ms
cookiematch
125 ms
100 ms
cse
233 ms
ProfilesEngineServlet
61 ms
82 ms
redirect
64 ms
sync
32 ms
rbcm
411 ms
gr
57 ms
tap.php
41 ms
tap.php
43 ms
tap.php
43 ms
rubicon
44 ms
rbcn
54 ms
IM0AS88O-1X-1J1M
88 ms
tap.php
70 ms
tap.php
54 ms
tap.php
56 ms
tap.php
59 ms
ProfilesEngineServlet
204 ms
pixel
110 ms
sd
59 ms
erb
109 ms
match
351 ms
rubicon
140 ms
rubicon_user_sync
162 ms
rc
123 ms
cm
93 ms
tap.php
80 ms
check
91 ms
tap.php
100 ms
blank.gif
94 ms
tap.php
110 ms
tap.php
109 ms
tap.php
109 ms
tap.php
104 ms
tap.php
97 ms
tap.php
96 ms
tap.php
83 ms
dk.html
78 ms
tap.php
84 ms
tap.php
78 ms
tap.php
73 ms
tap.php
74 ms
m
130 ms
tap.php
73 ms
ecc
80 ms
tap.php
74 ms
tap.php
62 ms
tap.php
83 ms
tap.php
73 ms
2.jpg
130 ms
tap.php
58 ms
tap.php
46 ms
tap.php
43 ms
tap.php
42 ms
tap.php
41 ms
tap.php
43 ms
tap.php
18 ms
tap.php
13 ms
tap.php
55 ms
optout_check
44 ms
get
59 ms
tap.php
9 ms
tap.php
11 ms
tap.php
11 ms
lephoceen.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
lephoceen.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
lephoceen.com SEO score
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lephoceen.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 Lephoceen.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.
lephoceen.com
Open Graph description is not detected on the main page of Le Phoceen. 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: