Tools & Wizards About Us
hallon.se screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

hallon.se

Mobilabonnemang, mobiltelefoner och bredband | Hallon

Page Load Speed

4.2 sec in total

First Response

463 ms

Resources Loaded

3.5 sec

Page Rendered

220 ms

hallon.se screenshot

About Website

Welcome to hallon.se homepage info - get ready to check Hallon best content for Sweden right away, or after learning these important things about hallon.se

Ingen bindningstid, ingen uppsägningstid, ingen faktura och alltid fast pris hos hallon – den enkla och billiga mobiloperatören.

Visit hallon.se

Key Findings

We analyzed Hallon.se page load time and found that the first response time was 463 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

hallon.se performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value2,640 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.104

88/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

hallon.se

463 ms

www.hallon.se

658 ms

646 ms

modernizr-latest.js

325 ms

jquery.min.js

40 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 13% of them (17 requests) were addressed to the original Hallon.se, 10% (13 requests) were made to Go.flx1.com and 9% (11 requests) were made to Eu-sonar.sociomantic.com. The less responsive or slowest element that took the longest time to load (667 ms) relates to the external source Ads.aftonbladet.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 618.8 kB (73%)

Content Size

847.8 kB

After Optimization

229.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Hallon.se main page is 847.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 750.9 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 34.2 kB

  • Original 50.6 kB
  • After minification 46.8 kB
  • After compression 16.3 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 34.2 kB or 68% of the original size.

Image Optimization

-29%

Potential reduce by 13.4 kB

  • Original 46.3 kB
  • After minification 32.8 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. Obviously, Hallon needs image optimization as it can save up to 13.4 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-76%

Potential reduce by 571.1 kB

  • Original 750.9 kB
  • After minification 515.4 kB
  • After compression 179.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 571.1 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 80 (85%)

Requests Now

94

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hallon.se

hallon.se

463 ms

www.hallon.se

www.hallon.se

658 ms

646 ms

modernizr-latest.js

modernizr-latest.js

325 ms

jquery.min.js

jquery.min.js

40 ms

466 ms

tag.js

tag.js

136 ms

tag.js

tag.js

370 ms

j.php

j.php

15 ms

eas

eas

667 ms

gtm.js

gtm.js

93 ms

bg3.png

bg3.png

129 ms

spritesheet.svg

spritesheet.svg

324 ms

icon-marker-soft-yellow2.png

icon-marker-soft-yellow2.png

118 ms

sprites-start.png

sprites-start.png

230 ms

icomoon.woff

icomoon.woff

137 ms

3fbbd6b1-cfa7-4ff0-97ea-af1b2c489f15.woff

3fbbd6b1-cfa7-4ff0-97ea-af1b2c489f15.woff

618 ms

6fb42ae0-a24e-4927-930d-47b462560e78.woff

6fb42ae0-a24e-4927-930d-47b462560e78.woff

573 ms

9aa32a81-1124-4c43-b3db-15bfb1f7aed2.woff

9aa32a81-1124-4c43-b3db-15bfb1f7aed2.woff

599 ms

460 ms

v.gif

v.gif

7 ms

analytics.js

analytics.js

41 ms

conversion_async.js

conversion_async.js

42 ms

jss

jss

375 ms

capture-apps-4.6.0.js

capture-apps-4.6.0.js

38 ms

hallon-se

hallon-se

205 ms

fbevents.js

fbevents.js

154 ms

iframe_api

iframe_api

42 ms

hallon-navigation.interface.js

hallon-navigation.interface.js

181 ms

startpage.interface.js

startpage.interface.js

202 ms

cookie-consent.interface.js

cookie-consent.interface.js

284 ms

linkid.js

linkid.js

8 ms

ec.js

ec.js

9 ms

76 ms

iframeStorage.html

iframeStorage.html

159 ms

www-widgetapi.js

www-widgetapi.js

26 ms

collect

collect

21 ms

collect

collect

83 ms

47 ms

103 ms

ga-audiences

ga-audiences

30 ms

view

view

134 ms

jquery.slidegallery.js

jquery.slidegallery.js

134 ms

iframeStorage.js

iframeStorage.js

7 ms

appsmanagerinit

appsmanagerinit

218 ms

bapi

bapi

162 ms

UserMatch.ashx

UserMatch.ashx

29 ms

sync.cgi

sync.cgi

264 ms

u.php

u.php

113 ms

serve

serve

51 ms

pixel

pixel

114 ms

usersync

usersync

59 ms

Pug

Pug

109 ms

210 ms

info.php

info.php

216 ms

tg-03.yieldpartners.com

tg-03.yieldpartners.com

235 ms

jss

jss

144 ms

merge

merge

22 ms

rum

rum

13 ms

64 ms

sd

sd

22 ms

match

match

54 ms

tap.php

tap.php

37 ms

232 ms

match

match

111 ms

match

match

406 ms

match

match

195 ms

match

match

195 ms

match

match

418 ms

cm.gif

cm.gif

34 ms

pixel.gif

pixel.gif

483 ms

mapuser

mapuser

93 ms

match

match

115 ms

match

match

190 ms

match

match

178 ms

match

match

124 ms

110 ms

roundtrip.js

roundtrip.js

26 ms

4-9505.js

4-9505.js

280 ms

P6ICSMSC3VHAZGVPIPVESK.js

P6ICSMSC3VHAZGVPIPVESK.js

163 ms

out

out

18 ms

tr

tr

29 ms

18 ms

22 ms

20 ms

18 ms

19 ms

tr

tr

35 ms

tr

tr

59 ms

tr

tr

75 ms

tr

tr

72 ms

out

out

6 ms

out

out

7 ms

out

out

14 ms

out

out

9 ms

out

out

10 ms

out

out

12 ms

out

out

12 ms

28 ms

u.php

u.php

45 ms

sync

sync

11 ms

sd

sd

8 ms

pixel

pixel

22 ms

adsct

adsct

94 ms

36 ms

36 ms

35 ms

34 ms

377928.gif

377928.gif

8 ms

in

in

26 ms

4-9505.js

4-9505.js

27 ms

in

in

7 ms

px

px

39 ms

ia

ia

25 ms

checkpoint

checkpoint

205 ms

ia

ia

28 ms

ia

ia

35 ms

hit.gif

hit.gif

44 ms

ia

ia

24 ms

ia

ia

16 ms

px

px

14 ms

ia

ia

14 ms

uid

uid

11 ms

uid

uid

12 ms

uid

uid

12 ms

pixel

pixel

19 ms

pixel

pixel

14 ms

uid

uid

10 ms

uid

uid

9 ms

Accessibility Review

hallon.se accessibility score

90

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

hallon.se best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

hallon.se SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    SV

  • Language Claimed

    SV

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hallon.se can be misinterpreted by Google and other search engines. Our service has detected that Swedish is used on the page, and it matches the claimed language. Our system also found out that Hallon.se 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.

Social Sharing Optimization

hallon.se

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