3.3 sec in total
237 ms
2.7 sec
351 ms
Click here to check amazing Hi Res content. Otherwise, check out these important facts you probably never knew about hi-res.pics
Turn your pictures to polaroid like photos.
Visit hi-res.picsWe analyzed Hi-res.pics page load time and found that the first response time was 237 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
hi-res.pics performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value11.3 s
0/100
25%
Value7.9 s
23/100
10%
Value70 ms
99/100
30%
Value0.046
99/100
15%
Value8.2 s
41/100
10%
237 ms
365 ms
356 ms
356 ms
291 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 97% of them (62 requests) were addressed to the original Hi-res.pics, 3% (2 requests) were made to Seal.entrust.net. The less responsive or slowest element that took the longest time to load (766 ms) belongs to the original domain Hi-res.pics.
Page size can be reduced by 767.5 kB (42%)
1.8 MB
1.1 MB
In fact, the total size of Hi-res.pics main page is 1.8 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. 30% of websites need less resources to load. Images take 811.4 kB which makes up the majority of the site volume.
Potential reduce by 160.0 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 160.0 kB or 79% of the original size.
Potential reduce by 46.9 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. Hi Res images are well optimized though.
Potential reduce by 533.6 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 533.6 kB or 69% of the original size.
Potential reduce by 27.0 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. Hi-res.pics needs all CSS files to be minified and compressed as it can save up to 27.0 kB or 85% of the original size.
Number of requests can be reduced by 5 (8%)
61
56
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hi Res. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
hi-res.pics
237 ms
www.hi-res.pics
365 ms
Default
356 ms
default.css
356 ms
jquery-3.7.0.js
291 ms
tinymce.min.js
766 ms
jquery.watermark.min.js
246 ms
WebResource.axd
267 ms
WebResource.axd
398 ms
Hi-Lo.png
90 ms
981d0457.jpg
402 ms
8ac3e3ae.png
89 ms
Transparent.jpg
91 ms
arial.jpg
90 ms
error_exclamation_icon.gif
87 ms
natural.jpg
296 ms
black.jpg
297 ms
blue.jpg
129 ms
green.jpg
130 ms
olive.jpg
134 ms
gold.jpg
190 ms
purple.jpg
190 ms
orange.jpg
191 ms
pink.jpg
251 ms
red.jpg
252 ms
yellow.jpg
255 ms
maple.jpg
312 ms
oak.jpg
312 ms
hickory.jpg
314 ms
frangipani-c.jpg
358 ms
fuschia-x.jpg
354 ms
hibiscus-x.jpg
437 ms
kiss.jpg
372 ms
crocodile.jpg
438 ms
fish.jpg
417 ms
giraffe.jpg
417 ms
iguana.jpg
433 ms
leopard.jpg
591 ms
rattle-snake.jpg
477 ms
tiger.jpg
477 ms
zebra.jpg
493 ms
pigeonhole.jpg
591 ms
bape-a-bathing-ape.jpg
591 ms
bape-camo.jpg
536 ms
3D.jpg
497 ms
sealv2.js
215 ms
haring.jpg
477 ms
eley.jpg
552 ms
deepsea.jpg
550 ms
tropics.jpg
539 ms
colette.jpg
640 ms
rotated-right.jpg
608 ms
PQ-8x10_Vertical-y_Border.jpg
606 ms
Motivational-Portrait-vertical-y.jpg
557 ms
Motivational-Landscape-Border.jpg
508 ms
PQ-8x10_Horizontal-x_Border.jpg
508 ms
film.jpg
580 ms
birds-feather.jpg
508 ms
birds-flying.jpg
505 ms
birds-wing.jpg
659 ms
rotated-left.jpg
622 ms
0b52b603.jpg
741 ms
entrust_site_seal_large.png
88 ms
btn_ListView.png
508 ms
hi-res.pics accessibility score
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
Form elements do not have associated labels
Links do not have a discernible name
hi-res.pics best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
hi-res.pics 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hi-res.pics can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Hi-res.pics 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.
hi-res.pics
Open Graph description is not detected on the main page of Hi Res. 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: