123.fr Site Title
Acces espace usagers
123.fr Meta Description
123.fr Test Results
123.fr Mobile Usability: 66/100
Size content to viewport
The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.
The page content is 4,082 CSS pixels wide, but the viewport is only 320 CSS pixels wide. The following elements fall outside the viewport:
<span id="availimportant">IMPORTANT: En…ant en veille.</span>falls outside the viewport.
Configure the viewport
Your page specifies a fixed-width mobile viewport. Consider using a responsive viewport to allow your page to render properly on all devices.
Configuring a viewport specifying width=device-width instead of width=320 will allow your page to adapt for devices of various widths. This may require additional work if the styling on your page relies on a fixed-width layout.
Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
The tap target
<a href="/index.html" class="bodydpoura"></a>and 10 others are close to other tap targets .
123.fr Mobile Speed: 59/100
Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://www.123.fr/macmars/genequestgene/genequestgene_01.jpg (expiration not specified)
Your page has 1 blocking script resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
71.3KiB of the HTML response was required to render the above-the-fold content. This requires 3 network round-trips. However, if the HTML response were compressed, then the HTML required to render the above-the-fold content could be delivered in just 2 network round-trips. Enable compression for the HTML response in order to prioritize the visible content for this page.
Only about 10% of the final above-the-fold content could be rendered with the HTML delivered within 2 round-trips .
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 68KiB (80% reduction).
Compressing https://www.123.fr/ could save 64.9KiB (81% reduction).
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 7.4KiB (24% reduction).
Compressing https://www.123.fr/macmars/wfrlonx/wfrlonx_11b.jpg could save 1.5KiB (51% reduction).
Reduce server response time
In our test, your server responded in 0.28 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
Minifying https://www.123.fr/traduc.20.js could save 811B (18% reduction).
Similar testsLast Tested: