180.no Site Title
180.no Test Results
180.no Mobile Usability: 60/100
Use legible font sizes
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.
Kundeloginand 1 others render only 5 pixels tall (13 CSS pixels).
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 1,074 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:
<div>Hei :)…Kommentar</div>falls outside the viewport.
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="/info/about" class="about-us-searc…nk isNotEmptyW">Om 180.no</a>and 1 others are close to other tap targets.
Configure the viewport
Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.
180.no Mobile Speed: 59/100
Your page has 5 blocking script resources and 5 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
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:
http://180.tns-cs.net/blank.gif (expiration not specified)
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 35.1KiB (71% reduction).
Compressing http://www.180.no/content/site?v=4bUikQZ22BQ0d-e6325LThXkiMrilk3TeuuSF63AIfc1 could save 23.5KiB (78% reduction).
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 701B (54% reduction).
Compressing http://www.180.no/content/img/green_glass.png could save 701B (54% reduction).
Minify HTML for the following resources to reduce their size by 678B (14% reduction).
Minifying http://www.180.no/ could save 678B (14% reduction) after compression.