2 sec in total
205 ms
1.4 sec
393 ms
Click here to check amazing SOMETHING SATURDAYS content for Norway. Otherwise, check out these important facts you probably never knew about somethingsaturdays.com
A blog by two people who are determined to do something new, go somewhere new, eat something new, or try something new every Saturday (or Sunday).
Visit somethingsaturdays.comWe analyzed Somethingsaturdays.com page load time and found that the first response time was 205 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
somethingsaturdays.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value9.8 s
0/100
25%
Value6.3 s
42/100
10%
Value620 ms
48/100
30%
Value0.017
100/100
15%
Value10.3 s
25/100
10%
205 ms
233 ms
7 ms
86 ms
75 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 25% of them (15 requests) were addressed to the original Somethingsaturdays.com, 25% (15 requests) were made to Cdn2.editmysite.com and 14% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (564 ms) belongs to the original domain Somethingsaturdays.com.
Page size can be reduced by 1.8 MB (62%)
2.9 MB
1.1 MB
In fact, the total size of Somethingsaturdays.com main page is 2.9 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. 65% of websites need less resources to load. Javascripts take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 37.1 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 37.1 kB or 80% of the original size.
Potential reduce by 1.1 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. SOMETHING SATURDAYS images are well optimized though.
Potential reduce by 1.8 MB
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 1.8 MB or 74% of the original size.
Potential reduce by 37.8 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. Somethingsaturdays.com needs all CSS files to be minified and compressed as it can save up to 37.8 kB or 49% of the original size.
Number of requests can be reduced by 28 (64%)
44
16
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SOMETHING SATURDAYS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
somethingsaturdays.com
205 ms
www.somethingsaturdays.com
233 ms
analytics.js
7 ms
sites.css
86 ms
fancybox.css
75 ms
social-icons.css
110 ms
main_style.css
81 ms
css
49 ms
jquery.min.js
83 ms
stl.js
134 ms
main.js
184 ms
stl.js
142 ms
css
71 ms
footerSignup.js
138 ms
jquery.jqtransform.js
272 ms
02d85e508ddbbddf89028eca4d23bdc21b9d83a6.js
29 ms
collect
27 ms
collect
67 ms
css
15 ms
collect
69 ms
1043724.jpg
268 ms
9832765.jpg
167 ms
8801389.jpg
252 ms
8258487.jpg
405 ms
9774201.jpg
267 ms
6626056.jpg
564 ms
9638266.jpg
404 ms
9733030.jpg
493 ms
5828194.jpg
491 ms
32623.jpg
441 ms
9314364.jpg
419 ms
footer-s48158ed9f7.png
55 ms
footer_signup.php
158 ms
sp.js
11 ms
Pru33qjShpZSmG3z6VYwnSZ2oysoEQEeKwjgmXLRnTc.ttf
6 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
9 ms
Jzo62I39jc0gQRrbndN6nXYhjbSpvc47ee6xR_80Hnw.ttf
9 ms
YTqeb6udKqDQr-y7rTKNruvvDin1pK8aKteLpeZ5c0A.ttf
60 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
26 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
26 ms
97uahxiqZRoncBaCEI3aWyZ2oysoEQEeKwjgmXLRnTc.ttf
26 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
25 ms
267447_5_0.woff
75 ms
267447_4_0.woff
104 ms
counter.js
24 ms
t.php
148 ms
ga.js
44 ms
quant.js
44 ms
t.php
140 ms
__utm.gif
16 ms
1043724.jpg
11 ms
footer-signup.css
138 ms
prototype.min.js
41 ms
utl.js
132 ms
footerSignupFrame.js
30 ms
placeholder_labels.js
118 ms
weebly_ensure_account.js
335 ms
267447_4_0.woff
173 ms
267447_5_0.woff
167 ms
somethingsaturdays.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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
somethingsaturdays.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
somethingsaturdays.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Somethingsaturdays.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Somethingsaturdays.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.
somethingsaturdays.com
Open Graph data is detected on the main page of SOMETHING SATURDAYS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: