Tools & Wizards About Us
hi-res.pics screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

hi-res.pics

Online Polaroid Photo Maker with Colorful Borders | Hi-Res.Pics

Page Load Speed

3 sec in total

First Response

186 ms

Resources Loaded

2.5 sec

Page Rendered

316 ms

hi-res.pics screenshot

About Website

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.pics

Key Findings

We analyzed Hi-res.pics page load time and found that the first response time was 186 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

hi-res.pics performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.074

95/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

hi-res.pics

186 ms

www.hi-res.pics

486 ms

Default

480 ms

default.css

359 ms

jquery-3.7.0.js

474 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 (832 ms) belongs to the original domain Hi-res.pics.

Page Optimization Overview & Recommendations

Page size can be reduced by 762.3 kB (42%)

Content Size

1.8 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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.

HTML Optimization

-79%

Potential reduce by 160.1 kB

  • Original 203.6 kB
  • After minification 195.5 kB
  • After compression 43.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 160.1 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 46.9 kB

  • Original 811.4 kB
  • After minification 764.5 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.

JavaScript Optimization

-68%

Potential reduce by 526.5 kB

  • Original 768.9 kB
  • After minification 751.8 kB
  • After compression 242.4 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 526.5 kB or 68% of the original size.

CSS Optimization

-91%

Potential reduce by 28.8 kB

  • Original 31.8 kB
  • After minification 20.8 kB
  • After compression 3.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 28.8 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (8%)

Requests Now

61

After Optimization

56

  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

hi-res.pics

hi-res.pics

186 ms

www.hi-res.pics

www.hi-res.pics

486 ms

Default

Default

480 ms

default.css

default.css

359 ms

jquery-3.7.0.js

jquery-3.7.0.js

474 ms

tinymce.min.js

tinymce.min.js

832 ms

jquery.watermark.min.js

jquery.watermark.min.js

248 ms

WebResource.axd

WebResource.axd

247 ms

WebResource.axd

WebResource.axd

190 ms

Hi-Lo.png

Hi-Lo.png

80 ms

981d0457.jpg

981d0457.jpg

471 ms

8ac3e3ae.png

8ac3e3ae.png

81 ms

Transparent.jpg

Transparent.jpg

106 ms

arial.jpg

arial.jpg

88 ms

error_exclamation_icon.gif

error_exclamation_icon.gif

79 ms

natural.jpg

natural.jpg

135 ms

black.jpg

black.jpg

135 ms

blue.jpg

blue.jpg

133 ms

green.jpg

green.jpg

149 ms

olive.jpg

olive.jpg

152 ms

gold.jpg

gold.jpg

201 ms

purple.jpg

purple.jpg

200 ms

orange.jpg

orange.jpg

201 ms

pink.jpg

pink.jpg

206 ms

red.jpg

red.jpg

213 ms

yellow.jpg

yellow.jpg

262 ms

maple.jpg

maple.jpg

263 ms

oak.jpg

oak.jpg

260 ms

hickory.jpg

hickory.jpg

266 ms

frangipani-c.jpg

frangipani-c.jpg

284 ms

fuschia-x.jpg

fuschia-x.jpg

325 ms

hibiscus-x.jpg

hibiscus-x.jpg

326 ms

kiss.jpg

kiss.jpg

322 ms

crocodile.jpg

crocodile.jpg

325 ms

fish.jpg

fish.jpg

345 ms

giraffe.jpg

giraffe.jpg

386 ms

iguana.jpg

iguana.jpg

384 ms

leopard.jpg

leopard.jpg

386 ms

rattle-snake.jpg

rattle-snake.jpg

389 ms

tiger.jpg

tiger.jpg

407 ms

zebra.jpg

zebra.jpg

446 ms

pigeonhole.jpg

pigeonhole.jpg

446 ms

bape-a-bathing-ape.jpg

bape-a-bathing-ape.jpg

447 ms

bape-camo.jpg

bape-camo.jpg

449 ms

3D.jpg

3D.jpg

431 ms

sealv2.js

sealv2.js

222 ms

haring.jpg

haring.jpg

441 ms

eley.jpg

eley.jpg

444 ms

deepsea.jpg

deepsea.jpg

436 ms

tropics.jpg

tropics.jpg

418 ms

colette.jpg

colette.jpg

429 ms

rotated-right.jpg

rotated-right.jpg

400 ms

PQ-8x10_Vertical-y_Border.jpg

PQ-8x10_Vertical-y_Border.jpg

448 ms

Motivational-Portrait-vertical-y.jpg

Motivational-Portrait-vertical-y.jpg

449 ms

Motivational-Landscape-Border.jpg

Motivational-Landscape-Border.jpg

433 ms

PQ-8x10_Horizontal-x_Border.jpg

PQ-8x10_Horizontal-x_Border.jpg

432 ms

film.jpg

film.jpg

395 ms

birds-feather.jpg

birds-feather.jpg

394 ms

birds-flying.jpg

birds-flying.jpg

441 ms

birds-wing.jpg

birds-wing.jpg

437 ms

rotated-left.jpg

rotated-left.jpg

431 ms

0b52b603.jpg

0b52b603.jpg

402 ms

btn_ListView.png

btn_ListView.png

398 ms

entrust_site_seal_large.png

entrust_site_seal_large.png

27 ms

Accessibility Review

hi-res.pics accessibility score

84

Accessibility Issues

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

hi-res.pics best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

hi-res.pics SEO score

96

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: