7.3 sec in total
487 ms
6.2 sec
571 ms
Welcome to prior.no homepage info - get ready to check Prior best content for Norway right away, or after learning these important things about prior.no
Forside
Visit prior.noWe analyzed Prior.no page load time and found that the first response time was 487 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
prior.no performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value3.1 s
76/100
25%
Value9.2 s
13/100
10%
Value170 ms
92/100
30%
Value0.552
13/100
15%
Value10.2 s
25/100
10%
487 ms
1902 ms
708 ms
2225 ms
233 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 87% of them (66 requests) were addressed to the original Prior.no, 7% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Prior.no.
Page size can be reduced by 688.2 kB (27%)
2.6 MB
1.9 MB
In fact, the total size of Prior.no main page is 2.6 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. 45% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 28.5 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 28.5 kB or 82% of the original size.
Potential reduce by 86.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. Prior images are well optimized though.
Potential reduce by 568.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 568.7 kB or 79% of the original size.
Potential reduce by 4.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. Prior.no needs all CSS files to be minified and compressed as it can save up to 4.2 kB or 80% of the original size.
Number of requests can be reduced by 38 (57%)
67
29
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prior. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
prior.no
487 ms
www.prior.no
1902 ms
style.css
708 ms
style.css
2225 ms
direct-edit-common.css
233 ms
style-contrast.css
238 ms
prototype.js
368 ms
scriptaculous.js
238 ms
sitecomponents.js
348 ms
site.js
357 ms
corefader.js
358 ms
tooltip.js
464 ms
lightbox.js
476 ms
rotationArticlelist.js
475 ms
slideshowtile.js
485 ms
slideelements.js
580 ms
categorydisplay.js
594 ms
toggleitemsarticlelisttile.js
594 ms
recipeselector.js
602 ms
jquery.js
817 ms
jquery-noconflict.js
709 ms
jquery.flot.js
834 ms
jquery.flot.pie.js
721 ms
piechart-jquery.js
820 ms
toolbarsuggestion.js
827 ms
categoryToggleMenu.js
838 ms
placeholder_polyfill.jquery.min.js
932 ms
tabs.js
937 ms
entitycomment.js
951 ms
offensivecomment.js
952 ms
CtXMLHttpRequest.js
955 ms
corepublish.js
1047 ms
css
24 ms
custom-se.js
1055 ms
builder.js
121 ms
effects.js
123 ms
dragdrop.js
120 ms
controls.js
128 ms
slider.js
118 ms
sound.js
120 ms
background.jpg
725 ms
sprites.png
1067 ms
prior-logo.png
159 ms
prior_egg_med_appelsin_460x260.jpg
450 ms
TipsTilDeleKyllingMiniatyr.jpg
409 ms
spiceupoppskrifter.jpg
428 ms
email.png%20%28thumbnail%29.png
313 ms
pavlova-med-jordber-rips.gif%20%28prior_articlelist_big%29.gif
699 ms
kylling-salsa-nottesalat-700x395.jpg%20%28prior_articlelist%29.jpg
568 ms
sjokoladecookies.jpg%20%28prior_articlelist_big%29.jpg
597 ms
eggerore%20med%20skinke%20varlok%20og%20tomat.jpg%20%28prior_articlelist_big%29.jpg
607 ms
eggerore%20m%20asparges%20sjampinjonger.jpg%20%28prior_articlelist_big%29.jpg
722 ms
eggerore%20rokt%20laks%20spinat%20pinjekjerner.jpg%20%28prior_articlelist_big%29.jpg
753 ms
grillp%C3%B8lser%20og%20kikertsalat.jpg%20%28prior_articlelist%29.jpg
779 ms
mnd_kokk_april_dessert.jpg%20%28164x112%29.jpg
856 ms
seige-sitronbiter.gif%20%28prior_articlelist_big%29.gif
891 ms
Wrap%20med%20kyllingp%C3%A5legg.jpg%20%28prior_articlelist%29.jpg
914 ms
Kyllingpai.jpg.jpg%20%28prior_articlelist_big%29.jpg
931 ms
banner_vinter_15-16.jpg
1300 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
9 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
9 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
32 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
32 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
31 ms
dark-background.png
957 ms
background-fold.png
1112 ms
background-bottom.png
1129 ms
ga.js
8 ms
Museo300-Regular-webfont.woff
1008 ms
Museo700-Regular-webfont.woff
1050 ms
Museo500-Regular-webfont.woff
1131 ms
__utm.gif
18 ms
spinner-large.gif
1093 ms
collect
64 ms
ga-audiences
39 ms
style-print.css
119 ms
prior.no 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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
prior.no 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
prior.no 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
Tap targets are not sized appropriately
NO
NO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prior.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it matches the claimed language. Our system also found out that Prior.no 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.
prior.no
Open Graph description is not detected on the main page of Prior. 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: